What you probably want is:
WSGIDaemonProcess mysite user=intrack group=intrack
python-path=/home/intrack/intrack_pythonenv/lib/python2.5/site-packages
processes=2 threads=25
WSGIProcessGroup mysite
WSGIScriptAlias / /var/www/wsgi_scripts/InTrack.wsgi
Thank you kindly, that took
2009/4/16 Alen Ribic alen.ri...@gmail.com:
What you probably want is:
WSGIDaemonProcess mysite user=intrack group=intrack
python-path=/home/intrack/intrack_pythonenv/lib/python2.5/site-packages
processes=2 threads=25
WSGIProcessGroup mysite
WSGIScriptAlias /
2009/4/16 Alen Ribic alen.ri...@gmail.com:
Ok that fixed the socket connection permission issue.
I confirm that all is working now.
The WSGISocketPrefix directive worked.
I just set mine to:
WSGISocketPrefix /tmp/wsgi
Preferably do not put it in /tmp, especially if this is a shared
So, try the 'run/wsgi' value first, with no leading slash.
I am running on a RedHat flavored distro, so:
WSGISocketPrefix run/wsgi
worked 100%.
Thank you again.
-Alen
On Apr 16, 10:25 am, Graham Dumpleton graham.dumple...@gmail.com
wrote:
2009/4/16 Alen Ribic alen.ri...@gmail.com:
2009/4/15 Alen Ribic alen.ri...@gmail.com:
I've seen a few posts related to Django, virtualenv and mod_wsgi
however still can't solve my problem.
I keep getting ImportError: No module named
django.core.handlers.wsgi in my apache error log no matter what I
try.
Read:
Thank you Graham for your reply.
You are definitely right about the permissions.
Apache User and Group directives are both set to 'apache'.
My wsgi (django) application is in the /home/intrack which is the
'intrack' user.
I added the WSGIDaemonProcess directive:
#
WSGIDaemonProcess user=intrack
