[ntp:questions] ntp not updating the time
unruh at wormhole.physics.ubc.ca
Wed Apr 14 23:57:44 UTC 2010
On 2010-04-14, Marc Fromm <Marc.Fromm at wwu.edu> wrote:
> I have tried the suggestions in the multiple replies and my server (RedHat 5.2) still will not correct its time. After 14+ hours it was over 28 minutes behind.
Something is seriously seriously wrong with the machine. If it is not a
VM, then the hardware is bad, or the initial clock configuration is very
bad, or the RTC is really bad.
Maybe a later kernel would help.
> I have a second server running fedora core 6, and from what I can see, the configuration of ntp is the same and its time is always spot on.
> I ended up creating a cron job that runs ntpdate -u every hour and that works.
> -----Original Message-----
> From: questions-bounces+marc.fromm=wwu.edu at lists.ntp.org [mailto:questions-bounces+marc.fromm=wwu.edu at lists.ntp.org] On Behalf Of Evandro Menezes
> Sent: Wednesday, April 14, 2010 10:32 AM
> To: questions at lists.ntp.org
> Subject: Re: ntp not updating the time
> I'd suggest soem sanity changes to the configuration file:
>> ?31 # Undisciplined Local Clock. This is a fake driver intended for backup
>> ?32 # and when no outside source of synchronized time is available.
>> ?33 server ?127.127.1.0 # local clock
>> ?34 fudge ? 127.127.1.0 stratum 10
> Remove these lines. Using your own host time as time reference for
> itself doesn't make sense in most situations.
>> ?36 # Drift file. ?Put this in a directory which the daemon can write to.
>> ?37 # No symbolic links allowed, either, since the daemon updates the file
>> ?38 # by creating a temporary in the same directory and then rename()'ing
>> ?39 # it to the file.
>> ?40 driftfile /var/lib/ntp/drift
> Sometimes, while playing with NTP configuration, you may end up with a
> bad driftfile. Stop NTP, delete /var/lib/ntp/drift and start NTP
> questions mailing list
> questions at lists.ntp.org
More information about the questions