The application NTP is used to synchronise time on Linux servers; this application when restarted was able to function as it should. The Linux kernel has some issues in dealing with the extra second; a patch is now in the works. Some distributions like Red Hat have already put out patches.
One of the applications affected was MySQL, the popular open source database, which runs mainly on Linux. German hosting company, Hetzner, experienced an increase in power usage of one MW at the time when the date changed.
The Mozilla Foundation experienced sharply increased loads on one server and used a little script, run via the Puppet system management software,to reset the date.
The bug was reported to the Debian GNU/Linux project shortly after midnight when developer Julian Gilbey noticed that MySQL was taking up loads of CPU on two different servers. Rebooting sorted the issue; obviously this is not an option for businesses that are running mission-critical applications.
Debian developer Russell Coker, who also experienced runaway CPU use on a server, said the issue should be viewed with concern by national governments.
"Hetzner is only one German hosting company and there's also a lot of private computer use that has mostly idle servers (eg. pretty much every corporate server I've ever run)," he wrote in a post to the Melbourne Linux user group, LUV
"It's easy to imagine this bug as having added a few hundred MW of load to the power grid. That sort of sudden load could cause a blackout. If the systems which manage the power grid to prevent cascading failures were also hit by the same bug then it would have been particularly nasty."
Google avoided problems by adopting a solution it dubbed as the "leap smear", modifiying its internal NTP servers so that a couple of milliseconds were added to every update. This was done over a time window before the leap second was actually added.