so it turns out having MaxRequestsPerChild set to 1000 was what was causing our 
mod_wsgi daemons to die.

we've been running a week now with MaxRequestsPerChild to 0 and haven't lost a 
single daemon.

.. so I think we're actually fine for our deployment now because we don't need 
to recycle our apache children anyway (that was leftover configuration from 
mod_python) but this is perhaps a bug in mod_wsgi...

Anyway, Graham I've taken your other advice and fixed our spare server 
limits/etc to reduce churn - all that stuff works well now too. We're in a much 
more stable state... thanks!

Alec


-- 
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