[ntp:questions] WARNING: someone's faking a leap second tonight
stevesommarsntp at gmail.com
Thu Aug 2 14:18:49 UTC 2012
One root cause involves a group of stratum one's peering each other. A
leap indicator can continue to circulate until the peering changes, or the
entire group is simultaneously reinitialized. This affects multiple
commercial server brands.
Is this a problem with some/all versions of ntpd?
On Thu, Aug 2, 2012 at 4:04 AM, Martin Burnicki <martin.burnicki at meinberg.de
> E-Mail Sent to this address will be added to the BlackLists wrote:
>> Martin Burnicki wrote:
>>> It turned out this happened with some older versions of
>>> ntpd when the customers had installed e.g. 3 or 4 servers
>>> for redundancy, and each NTP server had the other ones
>>> configured as upstream server (personally I know this is
>>> not a good configuration, but they did it anyway).
>> What kind of association were they, Peer, Server, AnyCast, ...?
> I remember at least one setup with 4 identical servers, where each server
> had a local GPS refclock configured (which for sure didn't send the leap
> warning anymore after the real leap second had passed) and in addition had
> simple "server" entries for the other 3 servers.
> Unfortunately this was mostly handled on the phone, so I don't have any
> records with details.
> Anyway, I'll see if we can install a similar setup here to see if we can
> duplicate this behaviour.
> Martin Burnicki
> Meinberg Funkuhren
> Bad Pyrmont
> questions mailing list
> questions at lists.ntp.org
More information about the questions