Bugzilla – Bug 153042
xntp failed to restart
Last modified: 2006-03-01 10:30:38 UTC
valkyrie:~ # date +%s.%N; rcntp restart; date +%s.%N 1140686991.630356000 Shutting down network time protocol daemon (NTPD) done Starting network time protocol daemon (NTPD) done 1140686992.084866000 valkyrie:~ # ntpq -p ntpq: read: Connection refused valkyrie:~ # rcntp status Checking for network time protocol daemon (NTPD): unused valkyrie:~ # date +%s.%N; rcntp restart; date +%s.%N 1140687141.443144000 Shutting down network time protocol daemon (NTPD) done Try to get initial date and time via NTP from ntp.suse.cz done Starting network time protocol daemon (NTPD) done 1140687142.861618000 valkyrie:~ # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 l 9 64 1 0.000 0.000 0.004 ns.suse.cz 195.113.144.201 2 u 8 64 1 0.377 0.048 0.004 /var/log/ntp: 23 Feb 10:29:51 ntpd[10274]: ntpd exiting on signal 15 23 Feb 10:30:01 ntpd[10294]: parent died before we finished, exiting 23 Feb 10:35:37 ntpd[25335]: synchronized to LOCAL(0), stratum 10 23 Feb 10:35:37 ntpd[25335]: kernel time sync disabled 0041 23 Feb 10:36:43 ntpd[25335]: synchronized to 10.20.0.2, stratum 2 23 Feb 10:37:46 ntpd[25335]: kernel time sync enabled 0001
well the first time obviously nothing was configured. are you sure there are no other things playing around with ntp.conf? like dhcp?
I run NetworkManager which happens to renew the lease every 30 minutes, but the config seems untouched: -rw-r--r-- 1 root root 2043 Apr 18 2005 /etc/ntp.conf
so this happens always when you restart ntp or was it just this once?
just once
well looks like the configuration didnt happen before that start and therefor it fails. Maybe some race with dhcp* setting ntp.conf and ntpd reading it. I cannot reproduce at all. If you see that again please let me know