Bug 153042

Summary: xntp failed to restart
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Martin Vidner <mvidner>
Component: NetworkAssignee: Hendrik Vogelsang <hvogel>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: suse-beta
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Martin Vidner 2006-02-23 09:47:19 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
Comment 1 Hendrik Vogelsang 2006-02-23 10:27:33 UTC
well the first time obviously nothing was configured. are you sure there are no other things playing around with ntp.conf? like dhcp?
Comment 2 Martin Vidner 2006-02-23 10:32:31 UTC
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
Comment 3 Hendrik Vogelsang 2006-02-23 11:40:32 UTC
so this happens always when you restart ntp or was it just this once?
Comment 4 Martin Vidner 2006-02-24 10:39:12 UTC
just once
Comment 5 Hendrik Vogelsang 2006-03-01 10:30:38 UTC
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