Jan Hoevers wrote: >> Interesting... >> That server is not open for ntpq queries, but it looks as if it's not >> syncing to anything except itself. What we see here is exactly the >> reason that we shouldn't use that LOCAL pseudo refclock driver.
> Just noted that 63.240.161.99 is still at stratum 2. I's mis configured > no doubt, but I'm wondering how. 63.240.161.99 is actually synced to time-a.nist.gov and if you query time-a.nist.gov you get one source there, the local clock, although it is synced by the ACTS dial service. Maybe there's something wrong with the ACTS service and time-a.nist.gov is unable to sync, so it's wandering and 63.240.161.99 is following it blindly, apparently. If that's the case, you'd think that the ntpd at 63.240.161.99 would have declared time-a.nist.gov a falseticker a long time ago and chosen one of its other configured servers. Given that it hasn't though it might indicate there are no other configured servers, which is never a good configuration as we all can see. -- 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
