[194312] in North American Network Operators' Group
Re: NTP problems/time.windows.com?
daemon@ATHENA.MIT.EDU (Eric S. Raymond)
Mon Apr 3 22:34:26 2017
X-Original-To: nanog@nanog.org
Date: Mon, 3 Apr 2017 22:34:21 -0400
From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Majdi S. Abbas" <msa@latt.net>
In-Reply-To: <20170404014615.GB24050@puck.nether.net>
Reply-To: esr@thyrsus.com
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Majdi S. Abbas <msa@latt.net>:
> Haven't seen it, but if people are reporting sudden hour
> offsets, on the first Monday in April, I'd bet on a DST implementation
> bug that hijacked the system clock on their servers.
>
> This doesn't look like the sort of error you'd get with a free
> running clock.
I concur, about the one-hour shift anyway. The random garbage times
aren't really likely either - jumps that large would tend to get the
source rejected as a falseticker.
It's a weird set of symptoms that rather looks as if they hit two different
failure modes at once. Dunno.
One of our NTPsec devs posted the link on one of our project channels and
suggested maybe we ought to call M$ with an offer of help...
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Please consider contributing to my Patreon page at https://www.patreon.com/esr
so I can keep the invisible wheels of the Internet turning. Give generously -
the civilization you save might be your own.
