You should also have the list of workers
with the DOCUMENTS they are currently serving.
If you don't, check if ExtendedStatus is On in httpd.conf.
If you're using any scripting engines server-side you probably
should check the limits on the resources your scripts may consume.
Like max_execution_time, memory_limit, mysql.connect_timeout and so on
if it's PHP.
> I have it running. I believe the lines that follow this one :
> Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request
> are the ones that are going to give me an answer.
> The start of the page gives me this information :
> Current Time: Tuesday, 28-Feb-2006 20:14:15 CET
> Restart Time: Tuesday, 28-Feb-2006 19:54:28 CET
> Parent Server Generation: 0
> Server uptime: 19 minutes 47 seconds
> Total accesses: 219 - Total Traffic: 1.4 MB
> CPU Usage: u5.88 s.8 cu0 cs0 - .563% CPU load
> .184 requests/sec - 1263 B/second - 6.7 kB/request
> 31 requests currently being processed, 5 idle servers
> This long after my swap space got filled. That only takes about 2 minutes. And doesn't get filled with Apache not running. The CPU load doesn't rise higher then 5%.
> If I understand the lines at the bottom of the page. And the direction you are heading at. Then my problem is site related. Only how do I know which one causes it. Or where do I have to pay the most attention at when looking at the outcome? Which always changes, I don't see anything looking different, or sticking out from the rest.
>>If you've enabled server-status handler
>>this might give you an idea of what apache threads are doing
>>when it's eating up your resources.
>>>That's just what buggers me the most. NO. If only I did I would know how to
>>>It's happening for some time now. Only since yesterday evening it's
>>>persistent. When it first came to my attention I was thinking at a cron job
>>>that triggered something, or a visitor. Even without any cron jobs running
>>>it's happening. And it is not visitor related. At least not as far as I can
>>>figure out true there IP-numbers and so on. I was thinking this because I
>>>had the impression that it happened on a regular basis, every two weeks or
>>>so. When I then stopped Apache for a few seconds and restarted Apache again
>>>everything was back to normal.
>>>I now have been uninstalling everything that I could miss for a while, even
>>>stopped Apache for several hours. No result. The only thing that happens is
>>>a very slow server.
>>>>Did you change something in the apache configuration or anything else?
>>>>>Just a question. Has anyone experienced the fact that Apache is eating up
>>>>>all the server resources and filling all swap space? Where do I find the
>>>>>reason why? Or in what log-file do I look for what reason? The server runs
>>>>>a Drupal based site if that should matter. Only after restarting Apache it
>>>>>directly goes true the roof. As well as I am at the moment.
>>>>>To be honest, it runs on Debian. I know, I know, if only I had the nerves
>>>>>to install Gentoo on it from a distance. Then I would be as happy as my
>>>>>home system running day after day without stopping, thanks to Gentoo. Only
>>>>>I don't want to surprise the hosting company and tell them to please fix my
>>>>>ssh connection. At least not for now ;-)
>>>>>Thanks in advance, why aren't all systems like Gentoo. It could also be
>>>>>possible that it's me being to stupid :-)
firstname.lastname@example.org mailing list