Another leap second (2016-12-31)

h17 · Wed Oct 26, 2016 10:32 am

Hi,

Last time it hurt us badly.
I assume problem has been fixed but... better save than sorry.
Just wanna ask if the fix is still present in the code
and haven't been lost during recent updates.

FYI, next leap second date:
December 31 2016 23:59:60 UTC

paulct · Wed Oct 26, 2016 10:37 am

And at what ROS version was it fixed?

h17 · Wed Oct 26, 2016 10:41 am

Last time affected were only CCRs (RouterOS v6).

paulct · Wed Oct 26, 2016 10:46 am

I am pretty sure I am safe, have some CCR's still on e.g 6.29 happily chugging along. - but just want to check which version it was fixed in - so I can double check.

h17 · Wed Oct 26, 2016 10:56 am

Wasn't hard to find:
http://forum.mikrotik.com/viewtopic.php ... eap+second

Unfortunately, there was a bug in our NTP package that caused a crash on CCR units due to the introduction of the Leap Second on June 30, 2015. This bug did not cause any other problems. We have fixed the issue in RouterOS v6.30rc26. No other devices were affected, only CCR units.

paulct · Wed Oct 26, 2016 11:29 am

Wasn't hard to find:
http://forum.mikrotik.com/viewtopic.php ... eap+second

Unfortunately, there was a bug in our NTP package that caused a crash on CCR units due to the introduction of the Leap Second on June 30, 2015. This bug did not cause any other problems. We have fixed the issue in RouterOS v6.30rc26. No other devices were affected, only CCR units.

Thanks

Sigh looks like I will need to upgrade a few, oh well.

Another leap second (2016-12-31)

Another leap second (2016-12-31)

Re: Another leap second (2016-12-31)

Re: Another leap second (2016-12-31)

Re: Another leap second (2016-12-31)

Re: Another leap second (2016-12-31)

Re: Another leap second (2016-12-31)

Who is online