I don't know If really need to write a script, this is so simple.
asa/root % ps -e -opid,ppid,cmd | grep http
15601381048577 /www/Web/servers/apache/2.0.54/bin/httpd -k start
15601631560138 /www/Web/servers/apache/2.0.54/bin/httpd -k start
10863961086105 grep http
From this output, you see that 1560163 is the child. Kill it with :
kill -KILL 1560163
If you enter again 'ps -e|grep http', you'll see (I am seeing...) the
number of httpd processes increasing until the max number (determined by
MaxClient and ThreadPerChild). When this max number is reached you get the
error message in main Apache error log.
Michel
--On mercredi 23 novembre 2005 19:30 -0500 Jim Gallacher
[EMAIL PROTECTED] wrote:
Michel Jouvin wrote:
Graham,
I played a little bit with worker MPM parameters. In particular I tested
your suggestion to increase to 2 StartServers. This has no effect on the
problem. I also tried to raise MaxSpareThread to MaxClient and
suppressed child recycling (MaxRequestPerChild=0) to suppress restart of
child as it seems to trig the problem with mod_pyton. No effect.
I also checked the load during all these tests. Almost no request. So
the heavy load syndroma you described doesn't seem to apply in this case.
Again, one month ago I tested during 2 or 3 days an Apache configuration
with mod_python loaded and without any url to trig its usages. And the
problem was already the same. So it seems this is not related to
mod_python usage (it happens even if you didn't execute any Python code)
but rather to mod_python interaction with other Apache components.
Michel
Michel,
I'm not able to reproduce the behaviour on debian stable (i386) with
apache 2.0.54, but I'm not sure if I'm testing this correctly.
Could you create a test script (bash or python) that will produce the
error? That way I can know for sure that I'm testing in the same way.
Jim
*
* Michel Jouvin Email : [EMAIL PROTECTED] *
* LAL / CNRSTel : +33 1 64468932*
* B.P. 34 Fax : +33 1 69079404*
* 91898 Orsay Cedex *
* France*
*
