Sounds like the symptoms recently experienced by some Linux servers caused
by the 61st (leap) second:
http://www.wired.com/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux/-
if so, it will require a reboot.
On Sun, Jul 8, 2012 at 4:37 PM, wrote:
> I have QNAP NAS running disk
1. The leap second happened at the end of June, a week ago. He reports that
it started earlier.
2. You don't need to reboot, it's possible to just re-set the clock, e.g.
"/etc/init.d/ntpd stop; date; date `date +”%m%d%H%M%C%y.%S”`; date;
/etc/init.d/ntpd start" (from
http://blog.contegix.com/2012/0
Greetings. This email is a gentle reminder that the linux.conf.au call
for mini-conferences closes in three days on 6 July 2012. Miniconfs are
day-long sessions on a specific topic: a miniature conference, with a
formal schedule published ahead of time listing speakers and sessions
for the day.
In
On Sun, July 8, 2012 9:53 pm, Amos Shapira wrote:
> 1. The leap second happened at the end of June, a week ago. He reports
> that it started earlier. 2. You don't need to reboot, it's possible to just
> re-set the clock, e.g. "/etc/init.d/ntpd stop; date; date `date
> +%m%d%H%M%C%y.%S`; date;
> /
