[ntp:questions] Re: 4.2.0 at 1.1161-r | Server dropped: strata too high | How to change this

Richard B. Gilbert rgilbert88 at comcast.net
Thu Feb 5 12:49:05 UTC 2004


How about issuing the command "ntpq -p"  on the server that's not 
synchronizing and posting the output?  That will tell us which internet 
servers it can see, if any.  My first guess would be that if it's not 
synchronized, it's because it can't establish contact with anything to 
synchronize with.

My second guess is that it might fail to synchronize because its own 
local clock is too far off.  If it's more than five minutes off, set the 
local clock to approximately the correct time before starting ntp.

Finally, it might be failing to synchronize because your local clock is 
drifting too fast.  If the undisciplined local clock gains or loses too 
much, it will never synchronize and stay synchronized.  The limit is 
about 500 parts per million.

Stefan Nicolin wrote:

>mayer at gis.net (Danny Mayer) wrote in message news:<3a2a0492.0402041231.53864044 at posting.google.com>...
>  
>
>>google at nicolinux.de (Stefan Nicolin) wrote in message news:<c5f87ac9.0402040626.138ce31d at posting.google.com>...
>>    
>>
>
>[...]
>  
>
>>>---
>>> 4 Feb 14:36:31 ntpdate[1758]: ntpdate 4.1.2 at 1.892 Tue Feb  3 12:28:16
>>>CET 2004
>>>(1)
>>>transmit(192.168.0.2)
>>>receive(192.168.0.2)
>>>transmit(192.168.0.2)
>>>receive(192.168.0.2)
>>>transmit(192.168.0.2)
>>>receive(192.168.0.2)
>>>transmit(192.168.0.2)
>>>receive(192.168.0.2)
>>>transmit(192.168.0.2)
>>>192.168.0.2: Server dropped: strata too high
>>>server 192.168.0.2, port 123
>>>stratum 16, precision -20, leap 11, trust 000
>>>refid [73.78.73.84], delay 0.02571, dispersion 0.00000
>>>transmitted 4, in filter 4
>>>reference time:    00000000.00000000  Thu, Feb  7 2036  7:28:16.000
>>>      
>>>
>>I'd be concerned where this date came from! That's 32 years into the future.
>>It's too far off to be valid. Check out that server at 192.168.0.2.
>>    
>>
>
>Erm, that's my ntpd server in charge... It's the one not syncronising
>- the whole thing I asked about.
>
>[...]
>
>  
>
>>If the date's too far off it won't reset itself without forcing it. Try using
>>the -g flag.
>>    
>>
>
>This didn't help
>
>
>Thanks anyhow.
>
>  
>
>>Danny
>>    
>>
>
>Stefan
>  
>



More information about the questions mailing list