why - "checktimeagainstUSNO" - on a fast boot fails anyway

[AussiePhil]

As per the subject,

Just rebuilt a Pi2 and during the initial reboot, it hung for maybe 2 minutes at that point, each subsequent boot the network has been up so the script just gracefully fails as network isn't up yet.

Now i know i have internet access as soon as i have IP but the script still hung first time.

[CaptainMurdoch]

It should be trying to ping github and if that is successful then it tries to get the time over http.  Are you sure it was that step and not something else cause the long delay?   The ping should timeout in a couple seconds and continue on without trying to get the time.

[AussiePhil]

nearly 100% positive Chris, I was watching the build/boot process on a projector. It could have been something else but nothing else got displayed for a couple minutes at that point.

Been trying to get a virtual matrix running but the Pi2 stability has been really bad with lot's of freezing so i have fully rebuilt and have fresh USB storage

[AussiePhil]

Make that 100%

Here's a capture (via photo) of the error

1. is the error from the check time..... there is a 2 to 3 minute delay, confirmed by time stamps between a couple of photos

2. is a secondary error i noticed

I would expect that if NTP is turned on that the check against USNO is not required and should be off.

[CaptainMurdoch]

Thanks for the screenshot, that gives line numbers and a couple other helpful error messages.  I will look into it.

The USNO time pull is on to catch the edge cases where NTP is on but blocked or is incorrectly configured.

[patdelaney]

I recall an issue a long time ago with software that our company wrote we had odd edge cases when the timezone was on the + side of GMT. I'm guessing AussiePhil is might be in Australia. So he would be on the + side of gmt and perhaps depending on the time of day he tries he maybe crossing over midnight math issue.


Just a thought

pat