On Tue, Jul 31, 2012 at 2:36 PM, Les Mikesell <[email protected]> wrote: > On Tue, Jul 31, 2012 at 2:17 PM, Andrew Melo <[email protected]> wrote: >> >> >>>> For some reason, if I watch top on my master while I browse around on >>>> the web interface, the java process stays pegged at 99-100% and it >>>> takes several seconds to render. Is there a common reason for that? I >>>> have 2Gb allocated to jenkins and the res is only 750MB, so I don't >>>> think it's GC churn. >>> >>> Is it running on a linux host that has been up since at least June >>> 30th? If so it could be the leap-second bug. If so, resetting the >>> time will fix it. >> >> Resetting the time (ntp?) or the jenkins server? >> >> Either way, it's been an issue since before then, but I'll give >> whichever one a try > > It is a linux kernel bug triggered by ntp on the day of a leap second. > Resetting the system time any way other than ntp will fix it. > For example: > date -s "`date`" > > But if it happened before June 30th or the system has been rebooted > since, this is not the problem.
Well, and it's only when i'm using the web interface (or if background stuff is happening) > > -- > Les Mikesell > [email protected] -- -- Andrew Melo
