On 28 June 2010 11:25, ssteinerX <[email protected]> wrote:
>
>> 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.
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.
1. Ensure you are using mod_wsgi 3.2 and not some older mod_wsgi 2.X
or 1.X version.
2. Change configuration to:
WSGIDaemonProcess batp user=batp group=batp threads=15 display-name=%{GROUP}
WSGIProcessGroup batp
Using that, the daemon process will be name (wsgi:batp) and you will
be able to see that using 'ps' and tools like 'htop' which can use a
overridden process name.
Now that you can distinguish easily with ps which is daemon process,
when it hangs see if it is running or not.
3. Also can change configuration to have:
WSGIDaemonProcess batp user=batp group=batp threads=15
display-name=%{GROUP} inactivity-timeout=60
WSGIProcessGroup batp
If all threads are getting stuck, but no actual dead lock, then the
inactivity timeout will cause process to be forcibly restarted after
60 seconds of no new requests being handled and no reads or writes by
the active requests.
4. Finally, make sure you have:
LogLevel info
in Apache configuration rather than default of 'warn'.
That way various stuff will be logged about when daemon processes are
started, die etc and you may be able to track what is happening.
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.
