We have a mod_wsgi 3.0c5 instance (just upgraded to 3.1 yesterday, but
haven't deployed the apache install with that version yet) that seems
to have this problem where some of the daemons don't restart when
they've lived their active lifetime. So what happens is the apache
runs along happily for days at a time, and then all the sudden (over
the course of a few hours) all the requests get slow, and the number
of occupied apache children (i.e. apache slots, not WSGI daemons) goes
way up. When I log into the machine, there are only a few (in one
example, only 7 of the original 48 that we started with) WSGI daemons
hanging on for dear life, handling as many requests as they can.
At the same time, we recently discovered (like a month ago) that we
had a C extension (jsonlib2) that was crashing the python interpreter
because of a refcounting bug. (We have since fixed the bug in
jsonlib2, if anyone here is using it!)
what I'm wondering is, if the WSGI daemon crashed hard (i.e. Bus
Error, etc) what is the expected behavior of mod_wsgi? It looks like
mod_wsgi should handle a SIGINT sent to a child, and restart the
daemon, but what about a crash?
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.
