Why so many dead NTP servers in pool.ntp.org?

Why so many dead NTP servers in pool.ntp.org?

Post by Rapha » Wed, 14 Dec 2005 08:23:15


when running the command

# ntptrace pool.ntp.org


more than half of the servers in the pool seem to be dead. Isn't
ntp.org responsible for polling servers and pruning the pool of dead
ones? What is a person to do to configure an ntp server if
pool.ntp.org is essentially unusable?
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Steve Kost » Wed, 14 Dec 2005 09:23:10


Please visit The NTP Pool web-site at http://www.yqcomputer.com/

The NTP Pool is operated separately from The NTP Project (R&D)
( http://www.yqcomputer.com/ ) and the NTP Public Services Project (Support)
( http://www.yqcomputer.com/ ).

--
Steve Kostecke < XXXX@XXXXX.COM >
NTP Public Services Project - http://www.yqcomputer.com/

 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Tapio Soku » Wed, 14 Dec 2005 11:37:48


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
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Tapio Soku » Wed, 14 Dec 2005 11:37:48


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
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Tom Smit » Wed, 14 Dec 2005 13:41:10


Yes. "ntpdate -q [server]" is a better test.
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Koos van d » Wed, 14 Dec 2005 18:16:17


(already answered in another followup)


pool.ntp.org is a separate organisation. Read http://www.yqcomputer.com/

And pool is very strict on monitoring the quality (both in being able to
get the time from a server and in getting a correct time).

See for example for our entry into pool.ntp.org
http://www.yqcomputer.com/

Koos van den Hout

--
Koos van den Hout PGP keyid 0x27513781 Camp Wireless
Mail XXXX@XXXXX.COM Use PGP when possible Wireless Internet
Phone +31-30-2534104 access at campsites
Fax +31-30-2513791 http://www.yqcomputer.com/
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by maye » Thu, 15 Dec 2005 02:28:08


Not at all. The pool was delegated. It is the responsibility of the pool
operators to maintain the DNS Records and of the operators of those
systems that provide pool service to update them as necessary.

One of the items on my work list is to implement the code to have ntpd
check each address returned and use it if NTP service is available and
to allow you to specify directly how many to use from the one address name.

Danny
_______________________________________________
questions mailing list
XXXX@XXXXX.COM
https://lists.ntp.isc.org/mailman/listinfo/questions
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by maye » Thu, 15 Dec 2005 02:33:49


I wasn't aware that it was using mode 6 NTP packets. It may be worth
while changing ntptrace to use normal mode 3/4 packets.

Danny
_______________________________________________
questions mailing list
XXXX@XXXXX.COM
https://lists.ntp.isc.org/mailman/listinfo/questions
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by David L. M » Thu, 15 Dec 2005 02:55:40

Danny,

Easy to add. I'm sure you have discovered the preempt keyword on the
server/peer command line. Should somebody implement the asynchronous
resolver, the whole thing would be completely automated.

Dave
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Rapha » Thu, 15 Dec 2005 07:08:53

On Tue, 13 Dec 2005 04:37:48 +0200, Tapio Sokura < XXXX@XXXXX.COM >




Thank you for your response. I am setting up the NTP daemon from
ntp.org and am a bit confused. In ntp.conf there is no mention of any
modes.

Currently I have been using rdate to set my system clock using
tick.greyware.com.

Now that I have installed NTP things have become more complex. It
seems that to configure it to be a server one also has to configure it
to be a client to some other NTP servers. I am not really sure what
is the daemon and what is the client portion of this program. The
config file for the daemon has a server parameter which makes it seem
as though it is a client. As far as configuring it as a server - if
for example I want it to be accessible to clients running "rdate"
(which is not mode 6?? not sure what "mode" it uses...) there don't
seem to be options in ntp.conf for this.

This is all so complex for a newbie. Unfortunately also the ntp
package doesn't contain standard man pages but refers you to html
documentation which seems to be more theoretical in nature but not
very useful for the practice of setting up a server.
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Rapha » Thu, 15 Dec 2005 07:20:38

On Tue, 13 Dec 2005 04:41:10 GMT, Tom Smith < XXXX@XXXXX.COM >





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.
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Bjorn Gabr » Thu, 15 Dec 2005 07:41:39

Raphae < XXXX@XXXXX.COM > writes:




The client is the server... ntpd is a client in that it get time from
the upstream servers you have configured in ntp.conf. Its a client in
that it will serve time to anyone that has your computer in his
ntp.conf. Its possible to block the serving part by using appropriate
'restrict' statements in ntp.conf.


rdate is another protocol than ntp. look at

http://www.yqcomputer.com/


Well, 'server your.prefered.ntp.server.com' in ntp.conf. Then start
ntpd with a 'ntpd -g'. Thats not to hard?

Its slightly more complex when you want your strange and old
gps-receiver running as a reference clock for ntpd to get its time
from.

Assuming you are running something unix-like. Does not your OS have
ntp already?

good luck,

Bjn
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by David Schw » Thu, 15 Dec 2005 09:29:30


NTP's job is to synchronize the clocks of machines that run it. It will
make things much easier if you meditate on that for a few minutes.

DS
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Steve Kost » Thu, 15 Dec 2005 12:07:56


Modes are not a user replaceable part.


rdate will set your system clock at a given instant but will not affect
your clock's long-term drift. ntpd, on the other hand, will reign in
your clock's long-term drift.


Please take a look at http://www.yqcomputer.com/
you'll find a short guide to getting ntpd configured.


ntpd is intended to be synchronized to a source of time: either a local
ref-clock (not the hardware clock) or a remote time server.

An ntpd will not serve time to others until it is synced.


ntpd is both a client and a server.


The 'server ...' line is one of the ways that you specify the time
sources your ntpd will listen to.


By default, ntpd will serve time to others without any special
configuration.


The Official documentation for the Reference Implementation of NTP
is currently distributed only as HTML. Manpages, or other forms of
documentation, are maintained by third parties.

Please take a look at the GettingStarted guide mentioned above.

--
Steve Kostecke < XXXX@XXXXX.COM >
NTP Public Services Project - http://www.yqcomputer.com/
 
 
 

Why so many dead NTP servers in pool.ntp.org?

Post by Steve Kost » Thu, 15 Dec 2005 12:11:47


<snip>


There may be a firewall blocking the NTP port (123/udp). Use the '-u'
option to make ntpdate use an unprivileged port.

--
Steve Kostecke < XXXX@XXXXX.COM >
NTP Public Services Project - http://www.yqcomputer.com/