On Thu, May 13, 2010 at 5:37 AM, Davo <[email protected]> wrote: > === Request to the WSGI is still running (timeout of 30 seconds not > reached yet) ====== > UID PID PPID C STIME TTY TIME CMD > davo 2844 2834 0 11:29 ? 00:00:00 > (wsgi:davo.com) -k start > davo 3443 2844 0 11:34 ? 00:00:00 watch -n 5 echo aaa > > === the request returned 500 error (normal timeout of 30 seconds...) > === > UID PID PPID C STIME TTY TIME CMD > davo 3468 2834 4 11:35 ? 00:00:00 > (wsgi:davo.com) -k start > davo 3443 1 0 11:34 ? 00:00:00 watch -n 5 echo aaa
The process in this case is called an "orphan process" rather than a zombie. http://en.wikipedia.org/wiki/Orphan_process Are you running this under Linux? If so, see what the process signal masks and such are. For example, $ cat /proc/3468/status | grep Sig $ cat /proc/3443/status | grep Sig Also determine the session ids of the processes, $ cat /proc/3468/sessionid $ cat /proc/3443/sessionid Do that both before and after you terminate the parent wsgi process. -- Deron Meranda http://deron.meranda.us/ -- 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.
