On 6 August 2010 05:15, colorpyen <[email protected]> wrote: > some interesting logs > > [info] mod_wsgi (pid=12985): Daemon process deadlock timer expired, > stopping process 'koistore'.
What are the WSGIDaemonProcess directive options you are using? That message above implies that some code in the application, normally a C extension module, acquired the Python GIL and then did a long operation which blocks, without releasing the GIL. The default deadlock timeout is 5 minutes however, so that the daemon process wasn't processing other requests should have been noticeable. Have you overridden the default deadlock timeout? Graham > [Fri Aug 06 02:46:12 2010] [info] mod_wsgi (pid=12985): Shutdown > requested 'koistore'. > [Fri Aug 06 02:46:17 2010] [info] mod_wsgi (pid=12985): Aborting > process 'koistore'. > [Fri Aug 06 02:46:17 2010] [error] [client 114.32.30.80] Premature end > of script headers: application.wsgi, referer: http://apps.facebook > [Fri Aug 06 02:46:17 2010] [info] mod_wsgi (pid=13088): Attach > interpreter ''. > [Fri Aug 06 02:46:17 2010] [info] mod_wsgi (pid=13088): Adding '/usr/ > local/pythonenv/DJANGO/lib/python2.6/site-packages' to path. > [Fri Aug 06 02:46:17 2010] [info] mod_wsgi (pid=13088): Create > interpreter 'www.evermai.com|'. > [Fri Aug 06 02:46:17 2010] [info] mod_wsgi (pid=13088): Adding '/usr/ > local/pythonenv/DJANGO/lib/python2.6/site-packages' to path. > [Fri Aug 06 02:46:17 2010] [info] [client 220.181.94.226] (32)Broken > pipe: core_output_filter: writing data to the network > [Fri Aug 06 02:46:17 2010] [info] [client 220.181.94.226] mod_wsgi > (pid=13088, process='koistore', application='www.evermai.com|'): Loadi > [Fri Aug 06 02:46:18 2010] [info] [client 220.181.94.226] (32)Broken > pipe: core_output_filter: writing data to the network > [Fri Aug 06 02:46:18 2010] [info] [client 220.181.94.226] (32)Broken > pipe: core_output_filter: writing data to the network > [Fri Aug 06 02:46:18 2010] [info] [client 220.181.94.226] (32)Broken > pipe: core_output_filter: writing data to the network > [Fri Aug 06 02:46:18 2010] [info] [client 114.45.139.105] (32)Broken > pipe: core_output_filter: writing data to the network > [Fri Aug 06 02:46:18 2010] [error] [client 220.181.94.226] Script > timed out before returning headers: application.wsgi > > On Aug 6, 3:05 am, colorpyen <[email protected]> wrote: >> I have been using wsgi3.0c in daemon for almost a year and recently >> upgraded to 3.3. Strange is now the server is not responding? >> >> Any help is appreciated.!! >> >> // server version >> Apache/2.2.14 (Ubuntu) mod_wsgi/3.3 Python/2.6.5 >> >> [Fri Aug 06 03:02:15 2010] [error] [client 220.181.94.226] Script >> timed out before returning headers: application.wsgi >> >> Thanks a lot. >> >> -peter > > -- > 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. > > -- 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.
