Bug 745381 - ntpd.service needs to be ordered after named.service
Summary: ntpd.service needs to be ordered after named.service
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ntp
Version: 15
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-12 08:07 UTC by Scott Shambarger
Modified: 2012-03-07 06:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-07 06:37:04 UTC
Type: ---


Attachments (Terms of Use)

Description Scott Shambarger 2011-10-12 08:07:38 UTC
Description of problem:
ntpd has errors at startup when it's unable to lookup the sync servers, eg  0.fedora.pool.ntp.org

Version-Release number of selected component (if applicable):
ntp-4.2.6p3-4

How reproducible:
Every boot on a server where ntp starts up before named can finish initializing (especially if ntpdate.service is not enabled).

Adding "named.service" to After= line in ntpd.service resolves the problem.

"network.target" should probably also be added to After= in case named.service is not enabled, but network.target is.

Comment 1 Miroslav Lichvar 2011-10-12 08:20:37 UTC
What errors exactly do you see? If it's not "host name not found (permanent)", it shouldn't be a problem, ntpd is designed to work even when started without network or working DNS.

Is the number of servers specified in ntp.conf equal to the number of servers reported by ntpq -pn?

Comment 2 Scott Shambarger 2012-03-07 06:36:34 UTC
Sorry, for some reason I never received the notification of your comment...

I upgraded to F16 in January, and no longer have copies of the F15 logs from Oct '11, so I'm afraid I can't paste them, or test ntpq -pn.

However, after upgrading to F16, I reverted to the 'shipped' ntpd.service file (and have ntp-4.2.6p4-1 installed), and I haven't seen the errors since.

The bug may still exist in F15, but I'm afraid I have no easy was to test it.  If no one else is reporting the issue, we might as well close the bug... I'll open a new bug if I encounter the issue again in F16.

Thanks!


Note You need to log in before you can comment on or make changes to this bug.