[ntp:questions] Re: Why so many dead NTP servers in pool.ntp.org?

Raphae prosolutions at gmx.net
Tue Dec 13 22:20:38 UTC 2005


On Tue, 13 Dec 2005 04:41:10 GMT, Tom Smith <smith at cag.zko.hp.com>
wrote:

>Tapio Sokura wrote:
>> Raphae wrote:
>> 
>>> when running the command
>>>
>>> # ntptrace pool.ntp.org
>>>
>>>
>>> more than half of the servers in the pool seem to be dead.  Isn't
>> 
>> 
>> Are you sure that they are dead, or just not responding to NTP control 
>> mode (mode 6) packets? Because mode 6 is what ntptrace uses, when the 
>> actual NTP time queries are sent/received using modes 1-5. All pool 
>> servers that I just tried did answer to normal time queries (mode 3) 
>> just fine. Some server operators choose to restrict mode 6 queries, that 
>> is completely acceptable by the pool rules.
>> 
>>   Tapio
>
>Yes. "ntpdate -q [server]" is a better test.

Here is the result of my running that command:

$ ntpdate -q pool.ntp.org
server 130.236.254.106, stratum 0, offset 0.000000, delay 0.00000
server 194.146.227.112, stratum 0, offset 0.000000, delay 0.00000
server 66.17.252.26, stratum 0, offset 0.000000, delay 0.00000
server 66.187.233.4, stratum 0, offset 0.000000, delay 0.00000
server 64.172.230.138, stratum 0, offset 0.000000, delay 0.00000
server 85.130.119.198, stratum 0, offset 0.000000, delay 0.00000
server 131.211.80.155, stratum 0, offset 0.000000, delay 0.00000
server 195.197.87.213, stratum 0, offset 0.000000, delay 0.00000
server 207.145.113.114, stratum 0, offset 0.000000, delay 0.00000
server 213.240.180.155, stratum 0, offset 0.000000, delay 0.00000
server 217.71.122.144, stratum 0, offset 0.000000, delay 0.00000
server 217.125.14.244, stratum 0, offset 0.000000, delay 0.00000
13 Dec 14:19:30 ntpdate[5334]: no server suitable for synchronization
found

I am in Silicon Valley, California.  I would assume that there are
some suitable servers in my immediate vicinity.




More information about the questions mailing list