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

[Kurt Roeckx]

On Wed, Oct 18, 2006 at 10:17:39AM +0200, Christoph Martin wrote:
> 
> I now have it running for over 12 hours with only one server to sync
> with and I still have the same problem. I initially set the time with
> ntpdate because I could not get ntpd to sync it:
> 
>  134.93.226.19   134.93.227.254   3 u    6   64  377    0.416  -469257
> 1570.32

So, this one it totaly off, and I wonder why it doesn't synchronize.

> The next server (134.93.226.19) is running sarge version of ntpd and
> successfully syncs:
> 
>  134.93.226.2    131.188.3.220    2 u  199 1024    3    0.983    2.203
>  0.310
> *134.93.227.254  192.53.103.108   2 u  443 1024  377    0.446   -0.277
>  0.340

This actually the first output that makes any sense so far.  Altough, I
have to wonder why the first peer only replied to the last 2 packets.

> 
> > 
> > If you ask me, atleast 134.93.226.2 and 134.93.226.19 aren't working
> > properly either.
> 
> The two proxies 134.93.226.2 and 134.93.227.254 have exactly the same
> setup (sarge) connecting to upstream servers and having eachother as peers:
> 
> 134.93.226.2 was recently restarted:
> 
> -134.93.227.254  192.53.103.108   2 u   24  128  376    0.337   -2.296
>  1.671
> +134.93.144.1    217.198.242.4    3 u   25  128  377    0.885    0.900
>  0.131
> *131.188.3.220   .GPS.            1 u   19  128  377    5.098   -1.001
>  0.592
> +192.53.103.108  .PTB.            1 u   21  128  377   20.641    1.520
>  4.802
> 
> 134.93.227.254 is running for longer:
> 
> -134.93.226.2    131.188.3.220    2 u   79  128  377    0.402    2.281
>  1.644
> +134.93.144.1    217.198.242.4    3 u  958 1024  377    0.830    3.377
>  0.013
> +131.188.3.220   .GPS.            1 u  966 1024  377    7.154    2.193
>  0.243
> *192.53.103.108  .PTB.            1 u  175 1024  277   29.349    7.485
>  5.884

Both look normal to me.

> To summerize it: 134.93.226.2 and 134.93.227.254 are firewall hosts
> which act as ntp proxies (and others). They have the same configuration
> and peer eachother. 134.93.226.19 is the internal network ntp server
> which connects to the two firewall proxies. Most of the other servers
> just connect to the internal server or additionally to the proxies.

So you have:
134.93.226.19 (int1) peers with:
- 134.93.226.2 (fw1)
- 134.93.227.254 (fw2)

fw1 and fw2 synchronize with external sources and peer with each other.

All 3 seem to be synchronize properly, atleast currently.

Some other hosts has all 3 of them as server, but does not synchronize.

In your previous mails you had 134.93.226.2 (fw1) always as stratum 5,
which doesn't make sense.

Anyway, it's recommended that you have atleast 3 peers with a higher
stratum and then peer with each other.  fw1 and fw2 only have 2 higher
stratum servers, peer with each other, and has a stratum 3 server too
which is probably totaly useless, even though it might give more
accurate time.


Kurt