Evandro Menezes wrote: > On Jan 1, 2:45 pm, Evandro Menezes <[email protected]> wrote: >> I'm happy that the pool can weed these guys out. > > However, I'm observing something interesting on my laptop, which has > clock3.redhat.com, a stratum 1 server which failed to add the leap > second, as one of its pool servers. > > As it returns from standby, because clock3.redhat.com is the only > stratum 1 server, NPT selects it as the primary reference, even if > other lesser stratum servers indicate that its time is not correct. > NTP eventually selects another lesser stratum server whose time is > convalidated by that of other servers, but only after several minutes. > > Here's the sequence of events: > t+00min: clock3.redhat.com is selected > t+11min: clock is stepped 650ms (curiously, not by a whole 1s) > t+29min: a stratum 2 server is selected > t+35min: clock is stepped -710ms > t+40min: clock3.redhat.com is selected > t+41min: a stratum 2 server is selected > > What this sequence seems to indicate is that NTP was eager to select a > stratum 1 server, in spite of its time not being validated by other > servers. Perhaps NTP should look to other servers, even lesser strata > ones, before pulling the trigger on a higher stratum server just > because its stratum is higher. > > HTH
You might complain to Red Hat and ask them to fix their server. Other than that, your only other remedy is to configure properly working servers in sufficient number to outvote the bad guys. The leap second was a problem last time and I suspect it will be a problem again in a few years! _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
