BTW, are you by chance also loading mod_python into the same Apache. If you are then disable it and do a full stop and start of Apache. The mod_python module can cause various conflicts, including causing daemon mode to not work in some rare cases.
Graham 2010/1/22 Graham Dumpleton <[email protected]>: > After about five minutes (value of Timeout in Apache configuration), > do you see a message in the Apache error logs about: > > Script timed out before returning headers: saweb.wsgi > > or: > > Premature end of script headers > > If you do, you may be getting affected by an issue also being seen on > FreeBSD in daemon mode for mod_wsgi 3.X. > > Also look for any other error messages about 60 seconds or 5 minutes later. > > May be helpful to ensure you have: > > LogLevel info > > or higher, eg., 'debug', set in Apache configuration. Look in both > virtual host and main Apache error logs. > > First off though, tell me whether problem occurs with a simple WSGI > hello world program, ie., don't use a Python web framework or large > application. > > If still occurs, then use mod_wsgi 2.8 instead for now. > > Am investigating the existing known issue, but don't have huge amount > of time and was only affecting FreeBSD and know that can use mod_wsgi > 2.8 instead. This doesn't mean it isn't a serious issue, but just too > overwhelmed with other personal and work stuff at moment to give it my > proper attention. > > Graham > > 2010/1/22 janedenone <[email protected]>: >> Hello, >> >> I tested mod_wsgi on my local system (OS X 10.6), and then installed >> the module on a virtual machine running Cent OS 5. Everything went >> fine, but the server (Apache/prefork MPM) does not reply when mod_wsgi >> is used in daemon mode. There is no error listed in /var/log/httpd/ >> error_log - the connection just times out. >> >> I did read about the potential issue with UNIX sockets, and added /var/ >> run/wsgi as my WSGISocketPrefix, so the socket is created correctly. >> >> In embedded mode, mod_wsgi works fine, but as soon as I uncomment the >> following >> >> # WSGIDaemonProcess djangoproject user=apache group=apache threads=10 >> # WSGIProcessGroup djangoproject >> >> nothing happens. What could cause this issue? >> >> Thanks, >> Jan >> >> -- >> 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.
