Bug 270341

Summary:	ntpd starts before networkmanager finishes setting up.
Product:	[Fedora] Fedora	Reporter:	charles harris <charlesr.harris>
Component:	ntp	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-09-17 15:20:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description charles harris 2007-08-31 06:23:56 UTC

Description of problem:
On boot, ntpd starts up before networkmanager finishes bringing up the network,
about 2 seconds early in fact, hence fails to find any time servers.

My workaround was to use S99ntpd in the level 5 startup and add a five second
sleep in the ntpd startup script. With these changes ntpd finds the servers, but
I'm sure there is a cleaner way to solve this problem.


Version-Release number of selected component (if applicable):
ntp-4.2.4p2-3.fc7

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Miroslav Lichvar 2007-08-31 08:34:53 UTC

ntpd should be able to use the new interface after a while (the default
interface update is 5 minutes). Have the servers specified in ntp.conf option
"dynamic"?

Comment 2 charles harris 2007-08-31 14:38:14 UTC

No, there is no "dynamic" option, ntp.conf is the standard Fedora version. The
problem was compounded by the fact that the default clocksource (tsc) drifted so
badly that ntpd never synchronized, so together with the initial failure to set
the clock, and resetting the hwclock on shutdown, I ended up with accumulated
errors of as much as 45 minutes -- rather unsettling. And no headsup message
either except grepping through the log.

Comment 3 Miroslav Lichvar 2007-08-31 17:12:22 UTC

For dynamic interfaces it's necessary to use the option. Default ntp.conf from
the package does that.

Comment 4 charles harris 2007-08-31 17:27:14 UTC

Hmm, I grepped dynamic in ntp.conf and didn't see it. I'll take a closer look
when I get back home as maybe it is under a different name. The install was from
the f7 live disk, is it possible that it differed from the full install?

Comment 5 Miroslav Lichvar 2007-08-31 18:07:37 UTC

system-config-date could overwrite the file, it doesn't support the option yet.
(bug #229217)

Comment 6 charles harris 2007-08-31 23:38:07 UTC

That must be it, because I don't see it. I wonder if ntpd will still synchronize
the system clock before starting if it finds the servers later?

Comment 7 Miroslav Lichvar 2007-09-03 12:29:53 UTC

The initial synchronization done by ntpdate? It's not delayed, so it will not do
any synchronization in this case.

Comment 8 Miroslav Lichvar 2007-09-12 15:03:18 UTC

Does ntpd work correctly when "dynamic" is used?

Comment 9 charles harris 2007-09-13 01:20:53 UTC

Yes, that seems to do the trick, ntpd came up about 30 seconds after the
network. Now let's see what happens if I fiddle with the clock... Sure enough,
the dynamic option went away.

Comment 10 Miroslav Lichvar 2007-09-17 15:20:16 UTC

Ok, I'm closing this as NOTABUG.