Hi
A week or so ago I noticed that ntpd had stopped syncing with time servers. running ntpq -pn, I would get something like the following:
Code:
ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
129.70.132.33 .INIT. 16 u - 64 0 0.000 0.000 0.000
77.245.18.26 .INIT. 16 u - 64 0 0.000 0.000 0.000
141.82.25.203 .INIT. 16 u - 64 0 0.000 0.000 0.000
37.187.7.160 .INIT. 16 u - 64 0 0.000 0.000 0.000
91.189.89.199 .INIT. 16 u - 64 0 0.000 0.000 0.000
I tried various things, forcing ipv6, using my ISPs ntp servers but wasnt getting any time results.
Running ntpdate gives the message " no server suitable for synchronization found"
I also tried running it in verbose:
Code:
ntpdate -d 91.212.90.20
18 Mar 09:10:36 ntpdate[5149]: ntpdate 4.2.6p3@1.2290-o Mon Aug 20 15:15:22 UTC 2012 (1)
Looking for host 91.212.90.20 and service ntp
host found : time.shf.uk.as44574.net
transmit(91.212.90.20)
receive(91.212.90.20)
transmit(91.212.90.20)
receive(91.212.90.20)
transmit(91.212.90.20)
receive(91.212.90.20)
transmit(91.212.90.20)
receive(91.212.90.20)
transmit(91.212.90.20)
server 91.212.90.20, port 123
stratum 3, precision -22, leap 00, trust 000
refid [91.212.90.20], delay 0.04265, dispersion 0.00047
transmitted 4, in filter 4
reference time: d6d28858.ae5c3141 Tue, Mar 18 2014 8:54:48.681
originate timestamp: d6d28c12.49ab8eb6 Tue, Mar 18 2014 9:10:42.287
transmit timestamp: d6d28c12.ef3a5f14 Tue, Mar 18 2014 9:10:42.934
filter delay: 0.04483 0.04300 0.04274 0.04265
0.00000 0.00000 0.00000 0.00000
filter offset: -0.65388 -0.65479 -0.65508 -0.65539
0.000000 0.000000 0.000000 0.000000
delay 0.04265, dispersion 0.00047
offset -0.655395
18 Mar 09:10:44 ntpdate[5149]: step time server 91.212.90.20 offset -0.655395 sec
Which suggests that ntp traffic is getting through, so not a firewall issue.
With this in mind, I installed openntpd package as opposed to the standard ntp package. Looking at the packet trace from tcpdump, I could see from syslog that it was syncronsising and had a list of valid peers, with messages like
openntpd[10234]: peer 46.8.40.31 now valid
(Unless I've missed something) A downside of openntpd is that it doesnt come with the binaries to query it with ntpq, so I'm not certain what its status is.
Does anyone have any ideas of things I might have missed for debugging the standard ntp? I have made sure iptables and ufw aren't interfering, and it had been running the default ntp.conf without problems for a long time