[time-nuts] Leap second NTP fail

[Ben]

The team I work with was forced to outsource the NTP service to a telco 
(the largest in the Netherlands). Too bad they didn't handle the leap 
second well.

Some time after the leap second hundreds of servers and VM's reported 
NTP problems.

...
sys.peer - stratum 15, last reached 28 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
sys.peer - stratum 15, last reached 44 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
sys.peer - stratum 15, last reached 44 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
sys.peer - stratum 15, last reached 38 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
sys.peer - stratum 15, last reached 22 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
sys.peer - stratum 15, last reached 27 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
sys.peer - stratum 15, last reached 58 secs ago, stratum is too high 
(max allowed is 9) (synchronized on <redacted>)
...


Some applications did report an error in the log, but I didn't find any 
real problems (yet).