[ntp:questions] Re: Time shifts without reason and NTP terminates

Dale Worley worley at dragon.ariadne.com
Thu Dec 4 13:33:00 UTC 2003


"Mauro" <mauo- at interfree.it> writes:

>  1 Dec 15:27:47 ntpd[24359]: logging to file /var/log/ntp.log
>  1 Dec 15:27:47 ntpd[24359]: ntpd 4.2.0 at 1.1161-r Mon Dec  1 16:18:12 CET
> 2003 (1)
>  1 Dec 15:27:47 ntpd[24359]: signal_no_reset: signal 13 had flags 4000000
>  1 Dec 15:27:47 ntpd[24359]: precision = 1.000 usec
>  1 Dec 15:27:47 ntpd[24359]: kernel time sync status 0040
>  1 Dec 15:32:07 ntpd[24359]: synchronized to 172.16.200.14, stratum=2
>  1 Dec 15:37:25 ntpd[24359]: synchronized to 172.16.200.15, stratum=2
>  1 Dec 15:37:26 ntpd[24359]: synchronized to 172.16.200.14, stratum=2
>  1 Dec 15:52:30 ntpd[24359]: kernel time sync disabled 0001
>  1 Dec 18:00:17 ntpd[24359]: synchronized to 172.16.200.15, stratum=2
>  1 Dec 18:02:00 ntpd[24359]: no servers reachable
>  1 Dec 18:34:28 ntpd[24359]: synchronized to 172.16.200.14, stratum=2
>  1 Dec 18:34:28 ntpd[24359]: time correction of -3599 seconds exceeds sanity
> limit (1000); set clock manu
> ally to the correct UTC time.
> 
> As You can see, ntp works fine until, for an unknown reason, It terminates
> itself because the time correction exceeds sanity limit.
> It seems there is anything that change brutally the time shifting it to one
> hour later!

There are any number of things that might cause this, but my guess is
that for some reason, 172.16.200.14 suddenly reported time that was 1
hour in the past.  Would something be monkeying with its time at about
18:34?

And you might want to check into why, from 18:00 to 18:34, neither
server seemed to be reachable.  That's 34 minutes.

Dale



More information about the questions mailing list