[87652] in North American Network Operators' Group
Re: Leap second reminder - Check your NTP
daemon@ATHENA.MIT.EDU (Chris Adams)
Sat Dec 31 22:16:01 2005
Date: Sat, 31 Dec 2005 21:15:28 -0600
From: Chris Adams <cmadams@hiwaay.net>
To: nanog@nanog.org
In-Reply-To: <1EDC3E40-8788-43A6-A266-CAD29A50C87F@dragondata.com>
Errors-To: owner-nanog@merit.edu
Once upon a time, Kevin Day <toasty@dragondata.com> said:
> While I can't say anything broke on our network as a result of the
> leap second, a good percentage of our gear lost NTP sync or had some
> kind of NTP problem around midnight UTC. You may want to check your
> NTP status at some point, in case something drifted quite a way off
> and won't step itself back now because the difference is too great.
I watched my Tru64 5.1B and Linux 2.2-2.6 servers (NTP wasn't running on
my Solaris 9 server accidentally) and Juniper and Cisco gear, and they
all stayed in sync. The Linux systems logged:
Dec 31 17:59:59 kosh kernel: Clock: inserting leap second 23:59:60 UTC
17:59:59 lasted 2 seconds in local time (since the normal time zone data
doesn't pass through leap seconds).
I saw the following from JUNOS:
Dec 31 18:00:00 hsvrouter /kernel: microuptime() went backwards (8144133.847075 -> 8144132.881330)
Tru64 and Cisco didn't log anything.
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
