I'm attempting to run my Django sites with mod_wsgi rather than mod_python (RHEL 5). I attempted this with all of my sites, but obtain the same issue. I set up it the conventional way everybody suggests, but demands towards the site simply break.
<VirtualHost 126.96.36.199> DocumentRoot /wwwclients/thymeandagain ServerName thymeandagain4corners.com ServerAlias world wide web.thymeandagain4corners.com LogFormat "%h %l %u %t "%r" %>s %b "%i" "%i"" combined CustomLog /var/log/httpd/thymeandagain_access_log combined ErrorLog /var/log/httpd/thymeandagain_error_log LogLevel error WSGIScriptAlias / /wwwclients/thymeandagain/wsgi_handler.py WSGIDaemonProcess thymeandagain user=admin group=admin processes=1 threads=16 WSGIProcessGroup thymeandagain </VirtualHost>
import sys import os sys.path.append("/wwwclients") os.environ['DJANGO_Configurations_MODULE'] = 'thymeandagain.settings' import django.core.handlers.wsgi application = django.core.handlers.wsgi.WSGIHandler()
The daemon mod_wsgi should really spawn off isn't there, so demands just break and that i get a lot of "Not able for connecting to WSGI daemon process" errors within the logs. Can there be something concerning the WSGIDaemonProcess directive that's stopping development of the daemon? Thanks ahead of time for just about any help...
EDIT: I recieve this within the error log:
[WARN@1227228322.174175] mcm_server_readable():2582: timeout: Operation now happening: choose(2) call timed out for read(2)able fds [INFO@1227228322.174263] mcm_get_line():1592 [WARN@1227227903.249626] mcm_server_readable():2582: timeout: Operation now happening: choose(2) call timed out for read(2)able fds [INFO@1227227903.249712] mcm_get_line():1592 [Thu November 20 21:18:17 2008] [notice] caught SIGTERM, shutting lower [Thu November 20 21:18:18 2008] [notice] Digest: producing secret for digest authentication ... [Thu November 20 21:18:18 2008] [notice] Digest: done [Thu November 20 21:18:18 2008] [notice] mod_python: Creating 4 session mutexes according to 8 max processes and 64 max threads. [Thu November 20 21:18:18 2008] [notice] Apache/2.2.3 (Red-colored Hat) mod_python/3.2.8 Python/2.4.3 mod_wsgi/2.1-BRANCH set up -- returning to normal procedures
The issue is that mod_python does not go well along with mod_wsgi. I acquired into similar problem couple of days ago and everything began employed by me soon after I said out mod_python inclusion.
Attempt to search modwsgi.org wiki for "mod_python", In my opinion there is someone speaking relating to this somewhere in comments
The actual issue is permissions on Apache log directory. It's important to inform Apache/mod_wsgi to make use of another place for the UNIX electrical sockets accustomed to contact the daemon processes. See:
Here is extremely detailed description regarding how to integrate django with mod_wsgi.
Hardly any information to take... maybe something went wrong when producing mod_wsgi in your system? Would be the permissions set properly? Can user admin access /wwwclients/thymeandagain/? Exactly what does the mistake log show when when (re)beginning Apache?