Re: Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC

2014-07-01 Thread Tim Heckman
On Tue, Jul 1, 2014 at 12:35 PM, Majdi S. Abbas wrote: > On Tue, Jul 01, 2014 at 12:20:12PM -0700, Tim Heckman wrote: >> Our systems all have loopstats and peerstats logging enabled. I have >> those log files available if interested. However, when I searched over >> the files I wasn't able to find

Re: Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC

2014-07-01 Thread Majdi S. Abbas
On Tue, Jul 01, 2014 at 12:20:12PM -0700, Tim Heckman wrote: > Our systems all have loopstats and peerstats logging enabled. I have > those log files available if interested. However, when I searched over > the files I wasn't able to find anything that seemed to indicate this > was the peer who tol

Re: Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC

2014-07-01 Thread Tim Heckman
On Mon, Jun 30, 2014 at 7:27 PM, Majdi S. Abbas wrote: > On Mon, Jun 30, 2014 at 05:33:52PM -0700, Tim Heckman wrote: >> I just was alerted to one of the systems I managed having a time skew >> greater than 100ms from NTP sources. Upon further investigation it >> seemed that the time was off by al

Re: Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC

2014-07-01 Thread Daniël W . Crompton
That's strange as I remember reading this yesterday: NO leap second will be introduced at the end of June 2014. http://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat D. Oplerno is built upon empowering faculty and students -- Daniël W. Crompton

Re: Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC

2014-06-30 Thread Majdi S. Abbas
On Mon, Jun 30, 2014 at 05:33:52PM -0700, Tim Heckman wrote: > I just was alerted to one of the systems I managed having a time skew > greater than 100ms from NTP sources. Upon further investigation it > seemed that the time was off by almost exactly 1 second. > > Looking back over our NTP monitor

Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC

2014-06-30 Thread Tim Heckman
Hey Everyone, I just was alerted to one of the systems I managed having a time skew greater than 100ms from NTP sources. Upon further investigation it seemed that the time was off by almost exactly 1 second. Looking back over our NTP monitoring, it would appear that this system had a large time a