[ntp:questions] NTP will fail once a week

John Pettitt jpp at cloudview.com
Tue Feb 15 21:06:51 UTC 2005



Alain wrote:

>
>
> Brad Knowles escreveu:
>
>>>  How should I test if ntpd is seeing any server?. This would be even
>>>  better than testing IP changes.
>>
>>
>>     Look at the scoreboard output of "ntpq -p".  It should be pretty 
>> obvious if you've been online for a while and yet all your configured 
>> servers are still in the ".INIT." state.
>>
> What I am really asking is: what information do I have to test? Here 
> is what I get:
> [root at servnet1 root]# ntpq -p
>      remote           refid      st t when poll reach   delay   offset 
>  jitter
> ============================================================================== 
>
> +ntp1.pucpr.br   tick.ucla.edu    2 -  212 1024  377  195.895  -16.291 
>  0.258
> *paulo.hiway.com Tick.UH.EDU      2 -  981 1024  377  242.452  -17.407 
>  7.428
>  LOCAL(0)        LOCAL(0)        10 l   10   64  377    0.000    0.000 
>   0.015
>  200.137.65.100  bb3.pop-mg.rnp.  3 -  247 1024  377  2516.67  1146.10 
> 1237.74
>  titan.cais.rnp. 174.117.23.255   2 -  994 1024  373  2026.89  900.025 
> 880.936
>  cherokee.pop-pr ntp1.pop-df.rnp  3 -  229 1024  377  212.999    5.415 
> 1284.30
> -ns.pads.ufrj.br ns2.pads.ufrj.b  2 -  995 1024  177  1102.97  216.381 
> 210.572
> -cs.columbia.edu clepsydra.dec.c  2 -  231 1024  377  338.108  -11.103 
> 21.075
> +hydrogen.cert.u 207.126.98.204.  2 -  991 1024  377  381.415  -20.140 
> 23.029
>
Look for (reach == 0  for *all* non-local clocks)  and (LOCAL clock 
reach == 377)

this will detect that case when the system can't see the world but has 
been up long enough to have tried  (the LOCAL == 377 test)

John





More information about the questions mailing list