mod_wsgi issue: solved

[Toshio Kuratomi]

David Malcolm wrote:
> I've been trying to deploy rpmgrok (a Turbogears 1 app [1]) behind
> mod_wsgi, and finally figured out why mod_wsgi stopped working when I
> added a WSGIProcessGroup directive (which avoids having to start a new
> process per http request)
> 
> I know bpeck has had similar issues with his "beaker" code [2]
> 
> It was working on publictest14.fp.org, but not on my local workstation
> (both RHEL-5 running mod_wsgi from EPEL).
> 
> Attempts to browse led to no response coming from httpd, and no log.
> 
> It turned out, I had mod_python installed on the box.
> 
> Upon disabling "LoadModule python_module modules/mod_python.so"
> from /etc/httpd/conf.d/python.conf it worked.
> 
> Known issue?  http://code.google.com/p/modwsgi/wiki/InstallationIssues
> describes another mod_wsgi/mod_python incompatibility, but the symptoms
> seem different [3]
> 
I know that we had problems with mod_wsgi and mod_python running
together but don't know if it was the same issue.  At this point I
believe we aren't running mod_python anywhere (definitely not on the app
servers in any case).

-Toshio

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
Url : http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20090113/fc8c51f9/attachment.bin