Tru64 v5.1B : mod_python prevents httpd child restart after previous slave h
as crashed
----------------------------------------------------------------------------
----------

Key: MODPYTHON-110
URL: http://issues.apache.org/jira/browse/MODPYTHON-110
Project: mod_python
Type: Bug
Components: core
Versions: 3.2
Environment: HP Tru64 5.1B / Apache 2.0.55 with mpm-worker
Reporter: Michel Jouvin


(issue already discussed on the mailing list...)

I recently installed mod_python 3.2b5 on Apache 2.0.54/2.0.55. I am running 
with problems if httpd slave process segfaults or is killed. In this case, n
ew httpd child doesn't initialize properly and master process restart the ma
x number of processes/threa
ds. We are running Apache with the MPM worker (on Tru64 platform).

This behaviour appears only if mod_python is loaded into Apache. this doesn'
t seem to be related to mod_python usage : this can happen if you load mod_p
ython even if no URL is configured to use it. You can easily reproduce the p
roblem on Tru64 platform (t
ested on several systems with different configuration and different level of
 patches) by doing 'kill -KILL' of an Apache slave process.

This happens even on a server without any mod_python activity (no URL config
ured to run a Python script) and with only the Apache standard modules loade
d (no PHP, no SVN...). This is a real pain because on our production server 
we regularly have httpd chi
ld crashed because of PHP. In this situation, httpd master doesn't succeed t
o restart properly a new child.

[ Post a follow-up to this message ]