[Pool] v6 monitoring: broken, or just me?
timekeeper at miuku.net
Wed Jan 11 09:05:06 UTC 2012
> Is something wrong with v6 monitoring, or is it just me? If there was
> any kind of announcement bearing on this, I missed it.
The most relevant announcement is probably
it's stated that 2.pool.ntp.org will now include IPv6 NTP servers as
well, ie. the pool now officially supports IPv6 in production use.
> As far as I can tell, my v6 pool host's monitoring data hasn't been
> updated since Christmas Eve. The host is 2610:98:8001::9:0, and
> manually fetching
> www.beta.grundclock.com/scores/2610:98:8001::9:0?log=1 returns
> perfectly good data, except that it shows nothing after
beta.grundclock.com is the development site and its data is separate
from the actual pool.ntp.org data, except that the user accounts are
shared between the development and production sites. The set of NTP
servers is different between the sites, and the monitoring is also separate.
The monitoring on the development server does seem to work for my IPv6
servers, as can be witnessed by
and http://www.beta.grundclock.com/scores/2002:52b5:8c2b::e (pretty
colourful graphs for a server behind a 6to4 tunnel (I haven't added this
server to the production pool)).
That said, if you go to
http://www.beta.grundclock.com/scores/2610:98:8001::9:0 it'll say that
"This server is scheduled for deletion on December 25, 2011" and its
admin is ask, for whatever reason. This is the reason why the monitoring
has been stopped for that server. Perhaps he needed to test how deleting
IPv6 servers works and used your server as a guinea pig. Generally
speaking, data on the development servers may be rather volatile..
To re-enable monitoring of your IPv6 server, simply add it to the
production pool at https://manage.ntppool.org/manage
After it has been added, your scores will be shown at
More information about the pool