"Morningwood" <adam.asay@gmail.com> writes:

> Every couple of days a get a httpd process that just will not die
> normally, if I let it run it eventually eats up all time on the cpu.
>
> I've tweaked the tuneing parms in the httpd.conf, but I seem to be
> missing something.
>
> Can anyone suggest a way to prevent this from happening?
>
> Here is the section I've been changing.
>
> ServerLimit 32
> ThreadLimit 64
> StartServers 10
> MaxClients 150
> #Added by Adam Asay 030805
> MinSpareThreads 25
> MaxSpareThreads 100
> ThreadsPerChild 25
> MaxRequestsPerChild 5000
>
>
> The server serves about 200,000 requests a day if that s any.
>

While you are trying to debug this, you might want to add
the following to your httpd.conf file --

RLimitCPU 120

Pick a good number (in seconds) that you think should be
the max for any child process. At least that will kill it without
it consuming a lot of resources -- sometimes, if you monitor the
error log when the kill occurs, you may be able to tell what type
of request(s) is causing the problem. Can be hard with a busy server.

Hope this s.

--
John
__________________________________________________ _________________
John Murtari Software Workshop Inc.
jmurtari@following domain 315.635-1968(x-211) "TheBook.Com" (TM)
http://thebook.com/