Nelson Minar wrote:
> Ah, perverse time, you have to love it. Interesting find. I can't get it 
> to answer any NTP monitoring queries, how did you get it to divulge an 
> upstream time source?

If you add the server as a synchronization source, it will show its current 
system peer in the refid column of the 'ntpq -p' banner. You can do it on 
the fly with ntpdc so you don't have to restart the server, but you need to 
set up authentication to do it.

ntpdc> addserver 63.240.161.99 iburst
Keyid:
MD5 Password:
done!
ntpdc> quit
saturn:$ ntpq -pn
    remote           refid      st t when poll reach   delay   offset  jitter
============================================================================
*127.127.28.0    .PPS.          0 l    1   16  377    0.000    0.004   0.001
+127.127.20.0    .GPS.          0 l    2   16  377    0.000    9.082   3.955
x192.168.1.103   .WWVB.         1 u    7   16  373    0.173   19.874   0.041
+140.142.16.34   .USNO.         1 u  108  128  377   13.419    2.543   1.413
-132.249.20.88   .WWVB.         1 u  122  128  377   43.062    0.558   1.744
-216.218.254.202 .CDMA.         1 u  105  128  377   32.504    2.066   1.690
-198.60.22.240   .GPS.          1 u  106  128  377   53.792    2.345   2.845
  63.240.161.99   129.6.15.28    2 u   53   64    0    0.000    0.000   0.000

I think that server is DOA as that query was done 10 minutes after I added 
it as a source and still no reply.

> I think what's most interesting about this is we've found a case where 
> the pool's simple scoring mechanism isn't enough to identify an 
> obviously bad server. It's been serving lousy time for at least 4 days, 
> but decaying at a rate that it's score is still above the cutoff. Not 
> sure what the solution for that is. OTOH, it's only 300ms off. For 
> casual users who ask one server for the time, this one's close enough to 
> be useful. And for the time nerds who really care about < 100ms 
> accuracy, they're going to have multiple sources and hopefully will 
> ignore this turkey. So the damage isn't that bad.
> 
> PS: those are some ugly opentpd bugs you're talking about.
> 
> 
> http://www.pool.ntp.org/scores/63.240.161.99

-- 
Dennis Hilberg, Jr.     \  [EMAIL PROTECTED]
NTP Server Information:  \  http://saturn.dennishilberg.com/ntp.php
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers

Reply via email to