Apache lots of process

[Winnebago]

If look at the procedure register on my server and observe a whole bunch of procedure. The entire these processes are a difficulty to the server and I do not be familiar with how to protect this from happening. Does anybody be familiar with how to protect this OK. What I desire to protect happening is the user being capable to spawn the entire the processes in the first place. When the entire these procedures get spawned at once or similar to they did it slows the server to a crawl and causes Apache to become unsympathetic for a bit.

[Sabastiaan]

These are zombie processes, or dead procedure. You cannot exterminate the dead. The entire processes ultimately die, and when they do they become zombies. They consume approximately no resources, which is to be expected for the reason that they are dead. The reason for zombies is so the zombie's parent (procedure) is able to retrieve the zombie's exit status and resource procedure statistics. The parent signals the operating system that it no longer requirements the zombie by using one of the hang around () system calls. The zombie determine to go away if its parent dies- it determine to be "adopted" by in it which determine to do the wait().

[Visala28]

The CSF permits you to set a boundary to how much procedure is able to work under a username and you encompass the alternative to set CSF to kill the processes if exceeded. I be familiar with, this be supposed to not occur, period. Seems to me it's a difficulty with swapping out Apache processes, and then not being capable to kill them. I decreased MaxClients to presently 16 and it has not happened in the precedent day. I might envisage having additional processes than fit in memory by means of merely a small number of additional clients than that, and particularly with robots or some type of DOS attack attempt that I get each few days but then, it might be something completely dissimilar, I am not sure.

[teenQ]

First, my server is extremely unconscientiously loaded; it's hosting three sites, none of which are accepted, and I am lucky if I get .5 requests-per-minute on the whole server. That's in addition true at the same time as this difficulty is happening. The difficulty is that Apache is forking multiple processes (similar to it does) but they are staying up and by no means exiting. It reaches the MaxClients setting (presently 40) and then hangs, making the complete server unapproachable.

[Candace]

The part of the difficulty is that I am on a 256 slice and the MaxClients would not fit in substantial memory (swap is occupied by means of 40 Apache processes). Be supposed to I decrease that value to something that determine to fit in memory. Additional to be expected it's a difficulty in a number of Apache module, I am presently hunting it down in gdb, keeping the server in its dead state for a short time.

[OS-X-10+]

I am using mod_php5, mod_python, mod_dav_svn, and supplementary customary modules (mod_rewrite, etc). mod_python is for Trac, mod_php5 for the rest of the site, containing Wordpress and zenphoto. The PHP in addition has numerous modules of its own loaded, containing mysql, gd, sqlite, etc. But tranquil if an apache module hangs, there be supposed to be a number of kinds of Apache procedure extinction, accurate.

[Apple.Mac.Rocker]

You have to discover the cause of this was a WordPress bug in my case completed the server collapse by considerably looping requests to itself (trying to "fork" a innovative PHP procedure for cron-like performance). If you encompass Wordpress, that might be the cause, but it might in addition be something completely dissimilar causing the similar type of crash. Seems similar to lots of things be able to create this occur.