On Wed, Jan 27, 2010 at 8:46 AM, Dan Bunyard <danodemano@xxxxxxxxx> wrote:That's a good suggestion and should be followed, but relative to this
> @Mark
> I will do that the next time it happens. I will also trim down the modules,
> I think I had done a mass install of a bunch of things I needed but in the
> process picked up a lot of them that I don't/won't use.
problem symptom: I don't think that will help memory consumption much
on Linux. There's only one copy of the code in memory, none allocated
from swap, and modules rarely use that much heap unless they've been
configured
>sudo strace -o /tmp/tracefile -p PID
> @Jeff
> I will try that as well. I'm unsure how to do a strace either to be
> honest.
where PID is one of the high CPU httpd processes you picked at random
(run top, see which ones have high CPU)
Are they different requests at the time of the problem symptom perhaps?
> I can't imagine this is from shear number of requests. In the hour
> or so leading up to the event there are only 123 GET requests logged in the
> access_log file. That just about one every 30 seconds, I can't see that
> being a problem.
Otherwise, something "goes bad" and the app starts malfunctioning from then on.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx