Ntpd Troubles

NOYB

ntpd service stopped working.


Apr 15 16:53:26 ntpd[91522]: Listen normally on 3 bfe0 192.168.2.1:123 
Apr 15 16:53:26 ntpd[91522]: Listen normally on 4 lo0 127.0.0.1:123 
Apr 15 16:53:26 ntpd[91522]: Listen normally on 5 lo0 [::1]:123 
Apr 15 16:53:26 ntpd[91522]: Listening on routing socket on fd #26 for interface updates 
Jun 8 16:26:57 ntpd[91522]: 12.249.97.82 local addr 192.168.2.1 -> <null>Jun 8 16:27:14 ntpd[91522]: ntpd exiting on signal 15 (Terminated) 
Jun 8 16:27:15 ntpdate[5027]: Can't find host 0.pfsense.pool.ntp.org: hostname nor servname provided, or not known (8) 
Jun 8 16:27:15 ntpdate[5027]: no servers can be used, exiting 
Jun 8 16:27:21 ntpdate[7177]: Can't find host 0.pfsense.pool.ntp.org: hostname nor servname provided, or not known (8) 
Jun 8 16:27:21 ntpdate[7177]: no servers can be used, exiting 
Jun 8 16:27:27 ntpdate[8282]: Can't find host 0.pfsense.pool.ntp.org: hostname nor servname provided, or not known (8) 
Jun 8 16:27:27 ntpdate[8282]: no servers can be used, exiting 
Jun 8 16:27:32 ntp: Giving up on time sync after 3 attempts. 
Jun 8 16:27:32 ntp: Starting NTP Daemon. 
Jun 8 16:27:32 ntpd[11547]: ntpd 4.2.8p2@1.3265-o Thu Apr 9 14:27:03 UTC 2015 (1): Starting 
Jun 8 16:27:32 ntpd[11547]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid 
Jun 8 16:27:32 ntpd[11684]: proto: precision = 1.955 usec (-19) 
Jun 8 16:27:32 ntpd[11684]: Listen and drop on 0 v6wildcard [::]:123 
Jun 8 16:27:32 ntpd[11684]: Listen and drop on 1 v4wildcard 0.0.0.0:123 
Jun 8 16:27:32 ntpd[11684]: Listen normally on 2 bfe0 [fe80::20d:56ff:fe3b:b840%1]:123 
Jun 8 16:27:32 ntpd[11684]: Listen normally on 3 bfe0 192.168.2.1:123 
Jun 8 16:27:32 ntpd[11684]: Listen normally on 4 lo0 127.0.0.1:123 
Jun 8 16:27:32 ntpd[11684]: Listen normally on 5 lo0 [::1]:123 
Jun 8 16:27:32 ntpd[11684]: Listening on routing socket on fd #26 for interface updates 
Jun 8 16:28:02 ntpd[11684]: ntpd exiting on signal 15 (Terminated)</null>

Restarting it seems to have been successful. Though I'm not sure why this Thu Apr 9 date though and whether or not it is an indication of a problem.


Jun 8 22:31:55 ntpd[83381]: ntpd 4.2.8p2@1.3265-o Thu Apr 9 14:27:03 UTC 2015 (1): Starting 
Jun 8 22:31:55 ntpd[83381]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid 
Jun 8 22:31:56 ntpd[83505]: proto: precision = 1.955 usec (-19) 
Jun 8 22:31:56 ntpd[83505]: Listen and drop on 0 v6wildcard [::]:123 
Jun 8 22:31:56 ntpd[83505]: Listen and drop on 1 v4wildcard 0.0.0.0:123 
Jun 8 22:31:56 ntpd[83505]: Listen normally on 2 bfe0 [fe80::20d:56ff:fe3b:b840%1]:123 
Jun 8 22:31:56 ntpd[83505]: Listen normally on 3 bfe0 192.168.2.1:123 
Jun 8 22:31:56 ntpd[83505]: Listen normally on 4 lo0 127.0.0.1:123 
Jun 8 22:31:56 ntpd[83505]: Listen normally on 5 lo0 [::1]:123 
Jun 8 22:31:56 ntpd[83505]: Listening on routing socket on fd #26 for interface updates

hda

Well-know modus operandi. The ntpd is listening everywhere and sensitive to other service changes i.e. IP interrupts, not robust. Needs bootkick every now and then. I have it in service-watchdog list, with email notification.

KOM

DNS failure or timeout on their end? I always add a few more NTP sources just to be sure, and not rely just on ntp.org.

charliem

@NOYB:

Though I'm not sure why this Thu Apr 9 date though and whether or not it is an indication of a problem.

That's the date on which it was compiled … looks like you are using pfSense 2.2.2