Bug 140128

Summary:	ntp does not start correctly at boot
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Michael McCarthy <sysop>
Component:	Basesystem	Assignee:	Hendrik Vogelsang <hvogel>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael McCarthy 2005-12-19 13:33:02 UTC

The ntpd process does not start correctly on boot.  This happens on all of my 10.0 systems.  The process is started, but "ntp -q" only shows the "LOCAL" clock and none of the configured servers.  In addition, manually running "rcntp restart" needs to be done several times to get the daemon properly initialized.

Comment 1 Michael McCarthy 2005-12-19 13:34:20 UTC

(In reply to comment #0)
> The ntpd process does not start correctly on boot.  This happens on all of my
> 10.0 systems.  The process is started, but "ntp -q" only shows the "LOCAL"
> clock and none of the configured servers.  In addition, manually running "rcntp
> restart" needs to be done several times to get the daemon properly initialized.
> 

Sorry, thats "ntpq -p" to show the daemon status...

Comment 2 Dr. Werner Fink 2005-12-19 13:37:39 UTC

Nothing major due it work here. Hopefully it is not
a configuration problem. In case of a configuration
this bug would be invalid and the support should be
asked about.

Comment 3 Hendrik Vogelsang 2005-12-21 11:16:07 UTC

please provide me with details on your ntp setup...

Comment 4 Michael McCarthy 2006-01-04 13:06:32 UTC

After further investigation, the problem appears to be caused by DHCP not assigning an address right away during the network setup.  A message that DNS resolution is not yet available appears on the boot screen.  An address does get assigned later on in the boot process, but NTP does not retry attaching to the configured time servers and drops them off the list requiring a restart of ntpd.  Issuing "rcntp restart" does not restart the daemon properly the first time after logging in.  If during the boot process the network setup does not "go into background" or a static IP address is assigned, no problem exists.

Comment 5 Hendrik Vogelsang 2006-01-16 14:51:48 UTC

if you rely on the address to be there you have to use a static one of use other mechnisms then boot script dependencys. Stuff like pre/post scripts with ifup or something sorry..