Bug#393509: [pkg-ntp-maintainers] Bug#393509: ntp: does not adjust time

[Kurt Roeckx]

On Mon, Oct 16, 2006 at 06:28:17PM +0200, Christoph Martin wrote:
> 
> I updated one some of my systems ntp from sarge to current testing.
> On one of the systems ntpd is not adjusting the time after the inititial
> sync. 
> 
> ntpq shows an every increasing time difference:
> 
> ntpq -n -c peers
>      remote           refid      st t when poll reach   delay   offset
>      jitter
>      ==============================================================================
>       134.93.226.19   134.93.227.254   3 u   18   64  377    0.524
>       -14813. 1689.13
>        134.93.227.254  131.188.3.220    2 u   39   64  377    0.443
>        -15216. 2153.18
>         134.93.226.2    134.93.225.254   5 u   34   64  377    0.430
> 	-15255. 2167.75
> 
> After some days it is over an hour and I have to restart ntpd to get a
> sync once again. Only after every restart I get a sync.	

Does /var/log/daemon.log contain anything useful?  It says that it
synched once?  I'm guessing it says it synched to 134.93.227.254 in that
case.

Are you using the same config on all hosts?

The hosts seem to have a rather large difference in time between them.
It says:
-14813.
-15216.
-15255.

Which is 442 ms difference between the clocks.  I think ntp rejects all
clocks because they don't agree on the time.  I think the algorithm
requires 3 clocks to agree before it accepts them.

I also find it weird that the first (134.93.226.19) which says it's
synched to the second (134.93.227.254) has such a big difference in
time.  They all seem to be in the same network, so they really shouldn't
be different more than a few ms.

> reference ID:         [83.84.69.80]

Where does that 83.84.69.80 come from?  I didn't see that in your list
of peers?


Kurt