3 ms·
No need to panic; this event happend a few days ago, August 1. And no one's certain, but it seems just as likely this is a bug in NTP as it is a deliberate atte
by NelsonMinar 14y ago
No need to panic; this event happend a few days ago, August 1. And no one's certain, but it seems just as likely this is a bug in NTP as it is a deliberate attempt to crash unpatched Linux servers. The way ntpd manages the leap second flag is pretty complex and error prone.
Link to thread view of NTP list discussion: http://lists.ntp.org/pipermail/questions/2012-August/thread.html#33611 http://lists.ntp.org/pipermail/questions/2012-August/thread....
- mrud 14y agoFrom http://lists.ntp.org/pipermail/questions/2012-August/033626.html http://lists.ntp.org/pipermail/questions/2012-August/033626.... There are over 10 stratum one's that advertise LI=1 as of Wed Aug 1 14:18:51 UTC 2012. Unless this changes another false leap second could occur on August 31, 2012 So yes this was happening on July 31st but may happen as well on August 31.
- 0x0 14y agoThere is a need to worry, because AFAIK at least Debian hasn't provided patches yet, so come September servers might still be crashing. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679882 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679882
- xfs 14y agoThe fix needs backporting large patchset, yet the next leap second isn't announced. So no need to rush... just wait for a while and do QA. Typical mentality.