> >> Can you post details of WSGIDaemonProcess directive you are currently > >> using? > > > Sure, just this: > > > WSGIDaemonProcess batp user=batp group=batp threads=15 > > WSGIProcessGroup batp > > If that is your configuration, may not be the same issue. > > For your configuration the daemon process should stay persistent and > would not be restarted due to reaching maximum requests etc. > > The problem others are seeing is where daemon process is being > restarted because of maximum-requests option being used. For some > reason, the Apache parent process when prefork is used after a while > isn't detecting when child process exits and is not restarting it.
Ah, I understand. > In your case, it could be that the daemon process is still running, > but is dead locked in some way and so all threads are busy and not > accepting new requests. > > I would suggest the following. [snip] Wow, thank you, I really appreciate that! That will certainly keep me busy for a bit and, whatever the problem is, I'm sure I'll learn quite a bit about what's going on just by going through those steps. Thanks for your time, S -- 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.
