>  It would also
> perhaps be obvious as you would have zombies lying around that will
> not vanish and I recollect you claiming you don't have zombies lying
> around.
> 

Right, no zombies

> if the child cant be the cause then we go back to the parent process.
> One would have to trust the core Apache code though. Thus, only issue
> could be a mismatch between Apache core and APR/APR-UTIL shared
> libraries or a third party Apache module that is doing weird crap in
> context of Apache parent process to screw things up. What third party
> Apache modules are you using besides mod_wsgi?
> 

So we're not using any third party modules - in fact mod_wsgi is about as fancy 
as we get. 

I'm starting to think this is actually a subtle bug in APR at this point - I 
did some digging around in there and it turns out APR doesn't really use 
SIGCHLD to manage children. Instead it seems to check for children 
periodically... I'm also suspecting APR more specifically because very little 
of apache proper uses the apr_proc_other_child - the only real consumer in 
apache itself is mod_cgid, which I have to imagine gets very little real use.

Ultimately, it looks like the child-management code, i.e. notifying stuff via 
apr_proc_other_child_refresh seems to come from the event loop, and thus is 
kind of the responsibility of the MPM. We're using the prefork MPM, maybe 
there's a bug there, since it sounds like a lot of people use the worker mpm.

I'm going to see if we can try the worker MPM...

Alec





> Graham
> 
>>> Are you able to able to list any non mainstream third party Python
>>> packages you use?
>>> 
>>> FWIW, you are still the only report of this sort of issue that I
>>> recollect seeing which still makes me suspect it is something in the
>>> hosted web application itself that is causing the issue
>>> 
>>> Graham
>>> 
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "modwsgi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/modwsgi?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to