This is a quick note that mod_wsgi daemon processes are now incompatible with mod_python. Upgraded mod_wsgi earlier today in CentOS and saw the following note. I guess this limitation has been around for a while before affecting CentOS/RHEL:
################################################################################# # mod_python and mod_wsgi compatibility note ################################################################################# # mod_wsgi will deadlock if run in daemon mode while mod_python is enabled # do not enable both mod_python and mod_wsgi if you are going to use the # WSGIDaemonProcess directive # In previous version of mod_wsgi, apache would segfault when both mod_wsgi # and mod_python were enabled. This update does not guarantee that will not # happen. ################################################################################# # Do not enable mod_python and mod_wsgi in the same apache process. #################################################################################
Keep this in mind if you plan to mix both modules under the same Apache instance.
Update: As Graham pointed out in this comment, there is no issue if mod_python 3.3.1 is used. That’s great news because I would miss the flexibility of mod_python when it comes to request processing.
mod_wsgi incompatible with mod_python by George Notaras is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Copyright © 2010 - Some Rights Reserved
If this is the case it is only true if you are using an ancient mod_python version. If you are using mod_python 3.3.1 there is no issue. Unfortunately RHEL/CentOS distributions do I believe still carry an older mod_python version. Read ‘http://code.google.com/p/modwsgi/wiki/InstallationIssues#Incompatible_ModPython_Versions’ for more information.
Hi Graham. You are right. Thanks for the clarification. I have updated the post.
BTW, CentOS and RHEL use mod_python v3.2.8 and mod_wsgi v3.2.