[ntp:questions] Re: time reset +492.958589 s

Jörgen Tegnér jorgen.tegner at telia.com
Fri Jun 17 17:32:01 UTC 2005


On Thu, 16 Jun 2005 21:33:12 -0400, Richard B. Gilbert wrote:

> Jörgen Tegnér wrote:
> 
>>Hi all,
>>
>>last two days I've noticed several huge time resets in the syslog. Is
>>that to be expected? I certainly didn't.
>>
>>Example below
>>
>>Jun 16 11:42:32 burken ntpd[1834]: synchronized to LOCAL(0), stratum 13
>>Jun 16 11:52:04 burken ntpd[1834]: synchronized to 66.92.250.40, stratum
>>2 Jun 16 12:16:34 burken ntpd[1834]: time reset +492.958589 s Jun 16
>>12:20:54 burken ntpd[1834]: synchronized to LOCAL(0), stratum 13
>>
>>Can anyone suggest possible causes?
>>
>>burken is running ntpd version 4.20, Debian Sid's 1:4.2.0a+stable-8
>>
>>Thanks,
>>Jörgen
>>  
>>  
> Not to be expected at all!   Is there some problem with your network
> connection to 66.92.250.40?  It seems strange that your system would
> synchronize to the local clock, synchronize to 66.92.250.40 and then
> synchronize to the local clock again if everything were working properly.
> 
> After burken has been running for at least one hour, please post the
> output of "ntpq -p".   Also post a copy of /etc/ntp.conf

I have now what looks like a stable time. See my reply to David
Woolley describing the fixes.

burken:~# ntpq -p -n
     remote           refid      st t when poll reach   delay   offset  jitter
-194.145.249.108 192.36.143.151   2 u   71  256  377   18.822   13.792   2.746
*80.161.63.67    192.36.134.25    2 u  203  256  377   41.162   -1.750   6.105
+129.240.64.3    129.132.2.21     2 u  218  256  377   24.014    0.234   7.563
+213.239.202.209 208.184.49.9     2 u    4  256  377   54.706    1.538   4.520

The offsets have stabilised around the figures shown above.

Thanks for the help,
Jörgen
-- 
I'm kinda looking forward to the alzheimer's... I'll get to meet new
people every day. I'll never have take the blame for anything. I'll get
to meet new people every day.




More information about the questions mailing list