httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Harrell <>
Subject Re: [users@httpd] mod_status usage, identifying memory leaks
Date Mon, 10 Jan 2005 18:21:43 GMT
> On Mon, 10 Jan 2005 09:38:59 -0800, Roger Harrell
> <> wrote:
>> I've been trying to track down the cause of excessive RAM usage for some
>> time. I've tried mod_status, but it does not seem to yield the info I
>> need. I get a list of current requests associated with the PIDs, but
>> those current requests are not necessarily the request causing the problem.
>> example. I've got 12 Apache child processes. 4 of which are occupying
>> 14% of server RAM. This is excessive. So I use mod_status to try and
>> identify why this is happening. All mod_status tells  me (with extended
>> status on) is one current request each of these children is serving. In
>> each case they are serving pages utilizing different scripts, so it has
>> not given any information on which script might be the culprit. How can
>> I further isolate the problem?
> Change your LogFormat to include the PID, then you can work back in
> the access log to find all recent requests for that process and try to
> find the match.
> Joshua.

Trouble is the PID is for the child process so it can server a lot of 
requests, so that PID will be associated with many different scripts. 
This is the same trouble I'm having with mod_status. Am I missing something?


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message