Red Hat Bugzilla – Bug 407921
ntpd errors on boot up of Fedora 8
Last modified: 2009-01-09 00:23:42 EST
Description of problem:
Fedora 8 receives a failed status on the following server ntpd when trying to
sync the time. The same settings and time servers work successfully in Fedora 7
Version-Release number of selected component (if applicable):
Starting up Fedora 8 or restart of machine.
Steps to Reproduce:
1. Reboot or restart Fedora 8
2. Services are starting ntpd fails with ntpdate cannot find servers
3. The same servers are reachable when the machine is running and sync with no
Ntp time should start successfully when the operating system is booting to
report accurate time logging.
No errors from the time service.
Here is the errors from the /var/log/messages (these are the time servers from
Nov 16 15:41:41 localhost ntpdate: can't find host 0.fedora.pool.ntp.org
Nov 16 15:41:41 localhost ntpdate: can't find host 1.fedora.pool.ntp.org
Nov 16 15:41:41 localhost ntpdate: can't find host 2.fedora.pool.ntp.org
Nov 16 15:41:41 localhost ntpdate: no servers can be used, exiting
Nov 16 15:41:41 localhost ntpd: ntpd email@example.com Mon Sep 24 14:40:07
UTC 2007 (1)
If further information is needed please contact me at firstname.lastname@example.org -
Thanks, Scott Griffin.
Have you enabled NetworkManager?
Please remove servers listed in /etc/ntp/step-tickers file, this is similar to
Can you give me the steps to do this, I am not sure?
The following command will print the status of NetworkManager service:
If it's running, you have NetworkManager enabled and network is not configured
when ntpdate is started. To prevent the errors from occurring again you should
remove all lines in /etc/ntp/step-tickers file (or just remove the file), so
ntpdate won't be called in the boot process. Also, make sure there is "dynamic"
keyword after every server line in /etc/ntp.conf. The default ntp.conf has:
server 0.fedora.pool.ntp.org dynamic
server 1.fedora.pool.ntp.org dynamic
server 2.fedora.pool.ntp.org dynamic
(In reply to comment #3)
> To prevent the errors from occurring again you should
> remove all lines in /etc/ntp/step-tickers file (or just remove the file), so
> ntpdate won't be called in the boot process.
This will not help users who boot another OS from time to time and that OS is not capable of having UTC in the RTC.
- stop serious work to play a game
- load that other OS
- sync the clock in that OS as it will be off by a few hours (linux having UTC in the RTC as it should be)
- stop playing and boot back to linux
now the users will have their clock off ny a few hours. If ntpdate is called on boot and executes successfully there is no problem (and it used to work just fine that way but as the original reporter said it is broken now, also see 445229)
(In reply to comment #4)
But, as per Bug 445229 comment #9, it is possible to have the clock synced when the machine starts. There is no need to remove the step-tickers.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.