SLUG Mailing List Archives
Re: [SLUG] identifying heavy load
- To: lists@xxxxxxxxxx
- Subject: Re: [SLUG] identifying heavy load
- From: Craig Dibble <craig@xxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 09:18:35 +1000
- Cc: slug@xxxxxxxxxxx
- User-agent: Thunderbird 18.104.22.168 (X11/20060728)
Voytek Eymont wrote:
Expand your terminal to full screen and hit 'c' in top and it will show
you the command line that proces is running.
I need to move the cursor to the 'suspect line', yes ?
how do I do that in putty ?
in full screen putty session I'm still on top's upper line and 'c' gives
me only: 'show command line'
Er, no - c should just toggle the command column on or off to show the
full command line. If it doesn't work for you then 'h' should show you
the available options. Failing that, just try something like this:
ps wax -o cmd |grep [p]erl
And you should get a listing of all perl processes running (there are
numerous different ways you can call that ps command to get the same
result, before anyone points it out, just pick your favourite if you
At a guess I'd say you're running apache_modperl and something's running
it's a good idea to see if you can find out why
it's happening in the first place if you can, as in all likelihood it will
yes, I would like to find that out
as it was, when trying to restart apache, I ended up in a loop where it
failed to start up again, and, under the circumstances, I ended up
restarting the system (as I couldn't recall how to clear the problem...)
If you haven't cleared all the processes it won't restart. Try
'apachectl stop' first, (or apache2ctl), if that doesn't work, try
'killall apache' (or httpd, depending on your system), and if that
doesn't work try:
ps wax |grep [a]pache
and do a kill -9 on the PIDs, which is the brute force way of clearing it.