Recent Features
| |||||||||||||
Leaping seconds and looping serversLeaping seconds and looping serversPosted Jul 3, 2012 14:22 UTC (Tue) by bobsol (subscriber, #54641)Parent article: Leaping seconds and looping servers
I'm curious about the scope of this problem. Where the reports refer to a distribution, Debian or a derivative keeps coming up. My servers are RH or Slackware based; no problems.
(Log in to post comments)
Leaping seconds and looping servers Posted Jul 3, 2012 15:29 UTC (Tue) by ejr (subscriber, #51652) [Link]
And I haven't seen the problem on Debian (unstable & testing). Must be an interesting combination of factors.
Leaping seconds and looping servers Posted Jul 3, 2012 17:16 UTC (Tue) by Ringding (subscriber, #34316) [Link]
I have a RHEL 6.2 server that sent MySQL into the CPU-burning state, kernel 2.6.32-220.17.1.el6.x86_64.
Leaping seconds and looping servers Posted Jul 7, 2012 1:36 UTC (Sat) by BenHutchings (subscriber, #37955) [Link]
All kernel versions from the past few years have that bug.
The known bugs involving kernel hangs are:
1. Deadlock in printk at midnight (introduced in ???, fixed by commits b845b51, fa33507 in 2.6.29, 2.6.27.46, Debian package version 2.6.26-20)
When I saw the fix for bug 2 it appeared that the live-lock being described was introduced by bd33126 etc. (post-3.3) and therefore not possible in earlier versions, but I'm no longer certain of this.
So I'm still hoping to find out what went wrong in 2.6.32 and in 3.2 so these can be fixed in stable updates.
Leaping seconds and looping servers Posted Jul 3, 2012 18:32 UTC (Tue) by smoogen (subscriber, #97) [Link]
The problem was not just to any distribution.
My Fedora laptop running Chrome went 100% load during the leap second. My Fedora and RHEL server just running apache didn't.
However other RHEL and Fedora boxes reported issues depending on the software that was being run at that time.
Leaping seconds and looping servers Posted Jul 4, 2012 11:05 UTC (Wed) by man_ls (subscriber, #15091) [Link] My Debian testing machine went to 100% CPU with either Chrome or Firefox, the former load being quite irregular with many spikes and the latter a solid regular 100%. Luckily I have two cores and the second one seemed to be unaffected.The funny thing was that after stopping both browsers everything went back to normal, but restarting any of them CPU load went up again. I had never seen something like this, so I took it as a divine sign telling me to go to bed and didn't look back... until the first LWN report. My Debian stable SheevaPlug server displayed the deadlock, or something like it. That is a lot of bugs for a tiny second!
Leaping seconds and looping servers Posted Jul 4, 2012 9:09 UTC (Wed) by ftc (subscriber, #2378) [Link]
I had some problems with a java-based streaming server, where identical software was installed on one CentOS 6.2 machine and two Debian Squeeze ones.
The installation on CentOS was affected by the problem (i.e. java started using an insane amount of CPU due to timers expiring immediately), while the installations on Debian appeared to work fine.
Leaping seconds and looping servers Posted Jul 4, 2012 17:38 UTC (Wed) by Lennie (subscriber, #49641) [Link]
I've seen 64-bit Java on Debian having problems, but 32-bit Java on Debian was fine (even on the same machine).
So maybe you have 32-bit Java on Debian and 64-bit Java on CentOS ?
|
|||||||||||||