Problem with external aerial and galleonm time server just turned back on. I'm guessing this is telling me its not worked for 9 days?
Should I now force a poll or wait?
$ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
time-p1 .MSF. 1 - 9d 64 0 0.43 0.027 16000.0
time-s1 0.0.0.0 16 - - 1024 0 0.00 0.000 16000.0
*LOCAL(0) LOCAL(0) 9 l 25 64 377 0.00 0.000 10.01
Correct. NTP is falling back to using the internal (LOCAL) clock, probably not ideal.
Your "Reach" is also 0, so it never got out to the time server.
The current time server in use will have an "*" next to it, for example
remote refid st t when poll reach delay offset jitter
==============================================================================
*10.0.0.2 132.145.5.107 2 u 1008 1024 377 0.991 -0.179 0.987
nist.gov .STEP. 16 u - 1024 0 0.000 0.000 0.000
LOCAL(0) .LOCL. 10 l 35d 64 0 0.000 0.000 0.000
If the time is to adrift it may never sync, but from the looks of it your not syncing because you are never reaching the time servers, for whatever reason, fix that first. Then, if the time is still adrift, run a manual sync, wait 15 minutes and see if you a) Have "*" next to the time servers, b) It has reached it.
You can try to test this with ntpdate -d time-p1 time-s1 which should try to reach out to those servers. The TCP/UDP ports are both 123, so you may need to check that this is open for your server to get out on.
Robin