[Cialug] stuck load average and ntp?
David Champion
dave at dchamp.net
Fri May 15 11:08:26 CDT 2009
That's a dual-core Xeon processor. The thing that was odd was that the
load avg never changed all morning long... you'd think the numbers would
adjust.
I'm rebooting it now, will see if that fixes anything.
BTW, Dan was asking about ntp stuff the other day, this page explains
why you should use the "pool" servers, if you click on the North America
link, it will show you what to put in your ntp.conf. The onese that
Mandriva had by default were no longer responding, so I updated my
Mandriva server.
http://www.pool.ntp.org/
-dc
chris wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
>> The load average isn't coming from any file...don't know why you are
>> messing with wtmp...it is coming directly from the kernel/scheduler.
>> If you have a load average of 6 then you have 6 procs running. See the
>> second line of the top output "6 running", so you probably have runaway
>> procs consuming all CPU.
>>
>> Kill the procs or reboot and your load average will go down.
>>
>
>
> Almost right. Depends on how many cores he has. If it is a single core/cpu then there is 1 process running and 5.57
> waiting to run. Sometimes the scheduler does flake out for whatever reason and a process can get added to the que and
> never find it's way out often due to strange conflicts in priority levels. That's rare though.
>
> As for the loadavg, it can be found a file that happens to be populated by the scheduler, /proc/loadavg. Cat it out at
> any time for a peek.
>
> I'd be looking long and hard at your process list you might find the r flag useful.
>
>
> crr/arreyder at freenode
>
More information about the Cialug
mailing list