2.1 rel AMD64 - NTP service keeps stopping daily
-
2.1-RELEASE (amd64)
built on Wed Sep 11 18:17:48 EDT 2013
FreeBSD 8.3-RELEASE-p11I've been observing since 2.1 release the ntpd - NTP clock sync service keeps stopping on my machine so every morning when I check the firewall I keep having to restart it.
Any suggestions of what I can look for to find out why its stopping? Is there somewhere on the machine that logs all the events to a disk folder for example or is syslog the only/best way to go with getting those events?
TIA.
-
Hey!
What is the output of: /var/log/ntpd.log ?
Regards,
M
-
Below is a copy of the log.
What I suspected is something to do with snort so I've changed snort to no longer update every 6 hours but every 4 days and the ntp has stayed up up till now (hence the delay in posting a reply).
So I've changed snort back to update every 6 hours to see if the ntp stopping occurs again.
ntpdate[56540]: step time server 37.187.101.66 offset 0.893353 sec
ntp: Successfully synced time after 1 attempts.
ntp: Starting NTP Daemon.
ntpd[19658]: ntpd 4.2.6p5@1.2349-o Wed Jul 24 14:35:11 UTC 2013 (1)
ntpd[20496]: proto: precision = 0.838 usec
ntpd[20496]: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20
ntpd[20496]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
ntpd[20496]: Listen and drop on 1 v6wildcard :: UDP 123
ntpd[20496]: Listen normally on 2 msk0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[20496]: Listen normally on 3 re0 81.35.57.123 UDP 123
ntpd[20496]: Listen normally on 4 re0 fe80::922b:34ff:fe77:142e UDP 123
ntpd[20496]: Listen normally on 5 re1 192.168.16.8 UDP 123
ntpd[20496]: Listen normally on 6 re1 fe80::ca3a:35ff:feda:4efb UDP 123
ntpd[20496]: Listen normally on 7 re2 10.20.30.40 UDP 123
ntpd[20496]: Listen normally on 8 re2 fe80::214:6cff:fe33:6387 UDP 123
ntpd[20496]: Listen normally on 9 lo0 127.0.0.1 UDP 123
ntpd[20496]: Listen normally on 10 lo0 ::1 UDP 123
ntpd[20496]: Listen normally on 11 lo0 fe80::1 UDP 123
ntpd[20496]: Listen normally on 12 pppoe0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[20496]: Listen normally on 13 pppoe0 81.130.20.59 UDP 123
ntpd[20496]: Listen normally on 14 ovpns1 fe80::250:43ff:fe00:1009 UDP 123
ntpd[20496]: Listen normally on 15 ovpns1 10.15.10.1 UDP 123
ntpd[20496]: peers refreshed
ntpd[20496]: Listening on routing socket on fd #36 for interface updates
ntpd[20496]: ntpd exiting on signal 15
ntpdate[47111]: adjust time server 91.121.76.221 offset 0.003286 sec
ntp: Successfully synced time after 1 attempts.
ntp: Starting NTP Daemon.
ntpd[48356]: ntpd 4.2.6p5@1.2349-o Wed Jul 24 14:35:11 UTC 2013 (1)
ntpd[48433]: proto: precision = 0.838 usec
ntpd[48433]: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20
ntpd[48433]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
ntpd[48433]: Listen and drop on 1 v6wildcard :: UDP 123
ntpd[48433]: Listen normally on 2 msk0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[48433]: Listen normally on 3 re0 81.35.57.123 UDP 123
ntpd[48433]: Listen normally on 4 re0 fe80::922b:34ff:fe77:142e UDP 123
ntpd[48433]: Listen normally on 5 re1 192.168.16.8 UDP 123
ntpd[48433]: Listen normally on 6 re1 fe80::ca3a:35ff:feda:4efb UDP 123
ntpd[48433]: Listen normally on 7 re2 10.20.30.40 UDP 123
ntpd[48433]: Listen normally on 8 re2 fe80::214:6cff:fe33:6387 UDP 123
ntpd[48433]: Listen normally on 9 lo0 127.0.0.1 UDP 123
ntpd[48433]: Listen normally on 10 lo0 ::1 UDP 123
ntpd[48433]: Listen normally on 11 lo0 fe80::1 UDP 123
ntpd[48433]: Listen normally on 12 pppoe0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[48433]: Listen normally on 13 pppoe0 81.130.20.59 UDP 123
ntpd[48433]: Listen normally on 14 ovpns1 fe80::250:43ff:fe00:1009 UDP 123
ntpd[48433]: Listen normally on 15 ovpns1 10.15.10.1 UDP 123
ntpd[48433]: peers refreshed
ntpd[48433]: Listening on routing socket on fd #43 for interface updates
ntpd[48433]: Deleting interface #13 pppoe0, 81.130.20.59#123, interface stats: received=116, sent=116, dropped=0, active_time=26336 secs
ntpd[48433]: 91.236.251.29 interface 81.130.20.59 -> (none)
ntpd[48433]: Deleting interface #12 pppoe0, fe80::250:43ff:fe00:1009#123, interface stats: received=0, sent=0, dropped=0, active_time=26336 secs
ntpd[48433]: peers refreshed
ntpd[48433]: Listen normally on 16 pppoe0 81.134.73.113 UDP 123
ntpd[48433]: bind(39) AF_INET6 fe80::250:43ff:fe00:1009%10#123 flags 0x13 failed: Can't assign requested address
ntpd[48433]: unable to create socket on pppoe0 (17) for fe80::250:43ff:fe00:1009#123
ntpd[48433]: failed to init interface for address fe80::250:43ff:fe00:1009
ntpd[48433]: peers refreshed
ntpd[48433]: new interface(s) found: waking up resolver
ntpd[48433]: Listen normally on 18 pppoe0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[48433]: peers refreshed
ntpd[48433]: new interface(s) found: waking up resolver
ntpd[48433]: ntpd exiting on signal 15
ntpdate[8370]: adjust time server 147.251.48.140 offset -0.004131 sec
ntp: Successfully synced time after 1 attempts.
ntp: Starting NTP Daemon.
ntpd[11153]: ntpd 4.2.6p5@1.2349-o Wed Jul 24 14:35:11 UTC 2013 (1)
ntpd[11193]: proto: precision = 1.117 usec
ntpd[11193]: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20
ntpd[11193]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
ntpd[11193]: Listen and drop on 1 v6wildcard :: UDP 123
ntpd[11193]: Listen normally on 2 msk0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[11193]: Listen normally on 3 re0 81.35.57.123 UDP 123
ntpd[11193]: Listen normally on 4 re0 fe80::922b:34ff:fe77:142e UDP 123
ntpd[11193]: Listen normally on 5 re1 192.168.16.8 UDP 123
ntpd[11193]: Listen normally on 6 re1 fe80::ca3a:35ff:feda:4efb UDP 123
ntpd[11193]: Listen normally on 7 re2 10.20.30.40 UDP 123
ntpd[11193]: Listen normally on 8 re2 fe80::214:6cff:fe33:6387 UDP 123
ntpd[11193]: Listen normally on 9 lo0 127.0.0.1 UDP 123
ntpd[11193]: Listen normally on 10 lo0 ::1 UDP 123
ntpd[11193]: Listen normally on 11 lo0 fe80::1 UDP 123
ntpd[11193]: Listen normally on 12 ovpns1 fe80::250:43ff:fe00:1009 UDP 123
ntpd[11193]: Listen normally on 13 ovpns1 10.15.10.1 UDP 123
ntpd[11193]: Listen normally on 14 pppoe0 81.134.73.113 UDP 123
ntpd[11193]: Listen normally on 15 pppoe0 fe80::250:43ff:fe00:1009 UDP 123
ntpd[11193]: peers refreshed
ntpd[11193]: Listening on routing socket on fd #38 for interface updates
-
Just a bump to say this is still occurring and it seems to occur when snorts doing 4 or 6 hourly updates. Dont know if this a bug and its being tackled or not.
-
Circumvented this little bug with the Service Watchdog package. Add NTPD to the list of watched services and you're good. Havent noticed NTPD stopped since.
-
Good Idea! I didnt know about the service watch dog buts its downloading now. Thanks!
