2008/11/28 libertyaikido <[EMAIL PROTECTED]>: > > Hello there, > > I'm new to mod_wsgi so please be gentle. :) > > I'm trying to implement Django in "daemon mode" on mod_wsgi and I'm > having a strange problem where apache simply stops responding to > requests after a very short amount of time. > > The problem does not occur when using embedded mode, but I don't want > to use embedded mode. > > No errors are written to the log and it won't respond until an apache > restart. > > What is wrong may be glaringly obvious, but I'm not seeing it yet. > > Any thoughts as to why this may be happening? > > Thanks in advance for any help you can give.
Have you set: LogLevel debug in Apache main configuration, and in VirtualHost if also there? This will ensure that mod_wsgi outputs a lot more debugging information. Also perhaps read: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques Some of the logging middleware could perhaps be used there to track where in request it is getting up to if you can find specific URLs that trigger issue on demand. Worst case is you use gdb as documented to attach to daemon process and get dumpy of calling stack for all threads. Also see if setting: WSGIApplicationGroup %{GLOBAL} helps. Some third party C extensions do not work properly in sub interpreters. This will force application to run in main Python interpreter. Finally, disable mod_python if running it at same time. Other than that, reply with some of the setup information that others asked about. 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 -~----------~----~----~----~------~----~------~--~---
