The ntpdate service didn't wait for NetworkManager to configure the network and gave up when ntpdate failed to set the clock.
ntpdate may not have access to the Internet when it was run, failing to set the system clock.
If ntpdate fails, try it again few times in increasing intervals.
The system clock is set even when NetworkManager takes longer to configure the network.
Description of problem:
Basically copied from a Fedora 13 bug report (same issue)
ntpdate fails to get update with NetworkManager
Booting up I get an error from ntpdate unable to contact
NTP server because there is no network up.
100% of time
Steps to Reproduce:
1. Boot box up
2. Observe failure from ntpdate
ntpdate fails to get date/time update
ntpdate should wait for the network to come up.
Seemed to have been fixed in F14 with systemd. Not really an option on RHEL6.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Well I guess unless it's been addresses for 6.1 it will need moved to that version.
The same change can be used as the one in Fedora, but it will delay the boot.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.