[ntp:questions] systems won't synchronize no matter what

unruh unruh at wormhole.physics.ubc.ca
Mon Oct 25 10:38:40 UTC 2010


On 2010-10-24, Richard B. Gilbert <rgilbert88 at comcast.net> wrote:
> On 10/22/2010 2:24 PM, Florin Andrei wrote:
>> I've 3 machines that would not synchronize to NTP servers no matter
>> what. They always end up stratum 10. They are regular Dell servers,
>> kernel 2.6.18-128.7.1.0.1.el5, ntp 4.2.2p1-7.el5
>>
>> I tried to sync up to local NTP servers, I tried the US pool, I cleaned
>> up the drift file, nothing works, even though the initial offset is
>> really small (ntpdate seems to work).
>>
>>
>> Config file:
>>
>> server 10.10.16.65 iburst
>> server 10.10.16.64 iburst
>
> You need to configure at least one more server here, two more would be 
> better.

That is NOT his problem. One would be fine for looking at his problem. 
You are dealing with a different problem-- what if the two disagree on
the time? But neither give time. 

>
>> server 127.127.1.0 # local clock
>> fudge 127.127.1.0 stratum 10
>> driftfile /etc/ntp/drift
>> restrict 127.0.0.0 mask 255.0.0.0
>> restrict 192.168.3.0 mask 255.255.255.0 nomodify notrap
>> restrict default ignore
>
> Lose the restrict statements.  Getting it working first!
>
> You may have to ask your networking people to allow NTP traffic to get 
> through the firewall.  Port 123 should  be allowed.

He says ntpdate works. 

>>
>>
>> Command line:
>>
>> ntpd -d -s /var/lib/ntp/stats -x -u ntp:ntp -p /var/run/ntpd.pid
>>
>>
>> This is the state they end up in:
>>
>> # ntpq -p
>> remote refid st t when poll reach delay offset jitter
>> ==============================================================================
>>
>> ut12 .INIT. 16 u - 64 0 0.000 0.000 0.000
>> ut11 .INIT. 16 u - 64 0 0.000 0.000 0.000
>> *LOCAL(0) .LOCL. 10 l 2 64 77 0.000 0.000 0.001
>
> I don't see where you configured ut12 and ut11!!!!

I presume those are the names of 10.10.16.6{4,5}

>
> You need to wait a few minutes after startup before ntpq can tell you 
> anything useful!  I'd wait at least five minutes before issuing ntpq -p.
>
>




More information about the questions mailing list