[ntp:questions] Re: NTP does not sync when using pool.ntp.org

Dale Worley worley at dragon.ariadne.com
Mon Oct 6 12:26:37 UTC 2003


mike cook <michael.cook at wanadoo.fr> writes:
>   remote       refid       st t when poll reach   delay   offset  jitter
> ==============================================================================
>   LOCAL(0)   LOCAL(0)      10 l   56   64  377    0.000    0.000   0.004
> +SHM(0)     .DCF.          0 l   35   64  377    0.000   -0.328   0.055
> *SHM(1)     .DCF.          0 l   36   64  377    0.000    0.340   0.026
>   clock2.redhat.c 0.0.0.0  16 u    -  68m    0    0.000    0.000 4000.00
> ++++++++++++++++
> 
> +topaz.ad1810.co utserv.mcc.ac.u  3 u   22   64  377   70.132    2.717
> 0.145
> -clock2.redhat.c .CDMA.    1 u   48   64  377  164.060    6.505   0.025
>   NTP.MCAST.NET   0.0.0.0  16 u    -   64    0    0.000    0.000 4000.00
> 
> So for some reason I got two addresses mapping to clock2.redhat.com but
> only one is good.

My recollection is that if you have one address listed as a server
twice, one of them will "reach" and the other won't.  OTOH, you *are*
getting timing information from clock2.redhat.com, so it's OK.  The
real problem is that pool.ntp.org is giving you the same address
twice.

Dale



More information about the questions mailing list