Leap Second Bug Fix

Wired Enterprise reports –

“On Saturday, at midnight Greenwich Mean Time, as June turned into July, the Earth’s official time keepers held their clocks back by a single second in order to keep them in sync with the planet’s daily rotation, and according to reports from across the web, some of the net’s fundamental software platforms — including the Linux operating system and the Java application platform — were unable to cope with the extra second.

Many computing systems use what’s called the Network Time Protocol, or NTP, to keep themselves in sync with the world’s atomic clocks, and when an extra second is added, some just don’t know how to handle it.

The “leap second bug” hit just as the web was recovering from a major outage to Amazon Web Services, an online operation that runs as much as 1 percent of the internet. Some operations, including Google, saw the leap second coming and prepared for it, but others weren’t so diligent.”

The fix is to reboot all of your servers but that can prove to be problematic for any organization.  Downtime is not an acceptable result.  The open source community has found a way to fix the Leap Second bug without rebooting everything.

- at the commandline, run:
- It will return a number or a formatted date.
- if output is formatted, then run:
/etc/init.d/ntp stop; date; date `date +"%m%d%H%M%C%y.%S"`; date;
- if output is not formatted, and is a number (which means it's in UTC mode), run:
/etc/init.d/ntp stop; date; date -s "`date`"; date;

Related Posts