Scott Marlowe wrote:
> On Wed, Aug 19, 2009 at 9:40 AM, Phoenix Kiula<phoenix.kiula@gmail.com> wrote:
>> On Wed, Aug 19, 2009 at 11:37 PM, Andy Colson<andy@squeakycode.net> wrote:
>>
>>> Phoenix: run top again, and hit the '1' key. It'll show you stats for
>>> each
>>> cpu. Is one pegged and the others idle?
>> top - 10:38:53 up 29 days, 5 min, 1 user, load average: 64.99, 65.17,
>> 65.06
>> Tasks: 568 total, 1 running, 537 sleeping, 6 stopped, 24 zombie
>> Cpu0 : 17.7% us, 7.7% sy, 0.0% ni, 74.0% id, 0.7% wa, 0.0% hi, 0.0% si
>> Cpu1 : 6.3% us, 5.6% sy, 0.0% ni, 84.4% id, 3.6% wa, 0.0% hi, 0.0% si
>> Cpu2 : 5.6% us, 5.9% sy, 0.0% ni, 86.8% id, 1.7% wa, 0.0% hi, 0.0% si
>> Cpu3 : 5.6% us, 4.0% sy, 0.0% ni, 74.2% id, 16.2% wa, 0.0% hi, 0.0% si
>> Mem: 8310256k total, 8277416k used, 32840k free, 61944k buffers
>> Swap: 2096440k total, 16128k used, 2080312k free, 7664224k cached
>>
>
> OK, nothing looks odd except, as pointed out, the stopped, zombie and
> high load. The actual amount of stuff running is minimal.
>
> I'm wondering if you've got something causing apache children to crash
> and go zombie. What parts of this setup are compiled by hand? Are
Good point. Does Linux have "last PID" field in top? If so, you could
monitor it to find if it it's rapidly changing.
