NTP Startup on RH8 on PE500SC

Ben Russo ben at umialumni.com
Wed Dec 25 10:48:01 CST 2002


On Mon, 2002-12-23 at 13:37, JP Vossen wrote:
> On 23 Dec 2002, Ben Russo wrote:
> 
> > On Sun, 2002-12-22 at 16:02, JP Vossen wrote:
> > > My clock seems to go nuts on Monday AM when on backup runs.  I was hoping to
> > > get more NTP log detail to see if that helps.  I've also tried running
> > > "/sbin/hwclock -w" hourly, as a very long shot, to see if that would help.
> > > It doesn't seem to have.
> >
> > Can you explain what you mean when you say that the "clock seems to go
> > nuts"?
> 
> The system clock goes wildly WRONG to the point where it's off by more than
> 1000 seconds and NTP gives up and dies.
> 
> 
> > Give an example of the log messages or the output of commands that you
> > see?
> 
> I think There are other examples (not from me) in the list archives, but:
> 
> /var/log# zgrep sanity messages*
> messages:Dec 23 06:59:10 drake ntpd[566]: time correction of 2041 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
> messages.1:Dec 16 06:36:40 drake ntpd[19639]: time correction of 1036 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
> messages.2:Dec  9 06:39:07 drake ntpd[26654]: time correction of 1048 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
> messages.3:Dec  2 06:33:47 drake ntpd[16822]: time correction of 1012 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
> messages.4:Nov 25 08:09:48 drake ntpd[19742]: time correction of 1868 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
> 
Well, I have a wild stab in the dark?!?
But since nobody else seems to have the answer, then why not.
Maybe the backup job is syncing the clock with the backup server?
Have you checked the date/time on the backup server?
Maybe the backup server needs to be running ntpd?
Also, maybe try running ntpd in the foreground with nohup and debug
turned on and redirecting to a log file.  Then when it dies you might
get some more info?

-Ben.




More information about the Linux-PowerEdge mailing list