Symptom

Leap second is improperly added on the first occurrence, not added at all on the second occurrence, or added every day following a leap second event. Scenario 1: Leap second Fails to Update on the Second Occurrence The device may experience a failure to add a leap second after already having experienced one leap second. This will occur if the device has been in sync with the NTP server continuously between the two leap second events. NTP will update the time on the device to the correct time on the next NTP update. Scenario 2: Leap second Update Occurs Daily The device may experience a leap second every day after having experienced one leap second.

Conditions

These errors will only occur during and after a leap second has occurred as announced by the International Earth Rotation and Reference Systems Service (IERS).

Workaround

Scenario 1: Force NTP out of sync at least one time between the two leap second events to ensure the 2nd event is not missed. This can be accomplished by removing and reapplying the NTP configuration. Scenario 2: A)Reload is the only workaround for this scenario once it starts occurring. The message that is produced when the erroneous leap second is added every day has no actual impact on the device beyond a minor variation in the clock which will resync with the next NTP update that is received. Reload is the workaround for both scenarios or removing NTP 25 hours before the leap occurrence and adding after leap second occurs is another workaround

Further Problem Description