Apache2 Segmentation fault with wsgi_module
- by a coder
Apache 2.2.3 is running as an existing web server under RHEL 5. Attempting to set up Trac using wsgi_module.
RHEL 5 ships with python 2.4, so in order to use the current version of Trac (1.0) I needed to install it with easy_install-2.6.
Trac works with the default mod_python, however users strongly encourage not using this module as it is officially dead.
Using RHEL's package manager, I downloaded/installed python26-mod_wsgi.so. I backed up the httpd.conf, then made the following additions:
LoadModule wsgi_module modules/python26-mod_wsgi.so
#...#
WSGIScriptAlias /trac /www/virtualhosts/trac/deploy/cgi-bin/trac.wsgi
<Directory /www/virtualhosts/trac/deploy/cgi-bin>
WSGIApplicationGroup %{GLOBAL}
Order deny,allow
Allow from all
</Directory>
Next I moved trac.conf to trac.conf.bak (contains mod_python calls).
I tested the configuration using:
apachectl configtest
Syntax is OK. So I reloaded the server config using:
service httpd reload
At this time, all virtualhosted sites stopped responding. I restored my backup copy of httpd.conf, reloaded the server config, and the virtualhosted sites are being served again.
A quick look at the httpd error_log shows:
[Mon Oct 08 10:20:04 2012] [info] mod_wsgi (pid=28282): Initializing Python.
[Mon Oct 08 10:20:04 2012] [info] mod_wsgi (pid=28280): Attach interpreter ''.
[Mon Oct 08 10:20:04 2012] [debug] proxy_util.c(1817): proxy: grabbed scoreboard slot 0 in child 28283 for worker proxy:reverse
[Mon Oct 08 10:20:04 2012] [debug] proxy_util.c(1836): proxy: worker proxy:reverse already initialized
[Mon Oct 08 10:20:04 2012] [debug] proxy_util.c(1930): proxy: initialized single connection worker 0 in child 28283 for (*)
[Mon Oct 08 10:20:04 2012] [info] mod_wsgi (pid=28283): Initializing Python.
[Mon Oct 08 10:20:04 2012] [notice] child pid 28249 exit signal Segmentation fault (11)
[Mon Oct 08 10:20:04 2012] [notice] child pid 28250 exit signal Segmentation fault (11)
[Mon Oct 08 10:20:04 2012] [notice] child pid 28251 exit signal Segmentation fault (11)
There are many similar lines, this is just a snip of the log file.
Suggestions on what could be going on to cause the Segmentation faults?
