Just for information, I struggled with a similar issue for a day or so - embedded mode worked fine, but daemon mode would hang and eventually time out with 500 Premature end of script headers and no other log output from Apache or the application. This is on CentOS 5 with These RPM installs
httpd.i386 2.2.3-31.el5.centos.2 installed httpd-devel.i386 2.2.3-31.el5.centos.2 installed mod_python.i386 3.2.8-3.1 installed python.i386 2.4.3-19.el5 installed python-devel.i386 2.4.3-19.el5 installed mod_wsgi 3.1 was built from source. The problem turned out to be a mod_python conflict. I finally stumbled across this in InstallationIssues ---------------------------------------------------------------------------------------------- Incompatible ModPython Versions The dual loading of mod_python and mod_wsgi together has only been tested and verified as working for mod_python 3.3.1. It is possible that mod_python 3.2.X may also work, but older mod_python versions 2.7.X and 3.1.X may give problems. In particular, it has been noted that dual loading of mod_python 3.1.4 will cause mod_wsgi daemon mode to fail. This occurs because older mod_python versions setup threads differently when initialising the Python interpreter. This appears to cause the mod_wsgi daemon processes to deadlock on the Python GIL at startup. This would be evident through any request to a WSGI application delegated to that daemon process appearing to hang and the browser client having to timeout. ---------------------------------------------------------------------------------------------- In spite of my mod_python being 3.2.8 which "may also work", as soon as I stopped loading it, mod_wsgi daemon mode started working. -- 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.
