> 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
wrote:
> 2009/4/16 Alen Ribic :
>
>
>
> > Ok t
help.
-Alen
On Apr 16, 10:02 am, Graham Dumpleton
wrote:
> 2009/4/16 Alen Ribic :
>
>
>
>
>
> >> What you probably want is:
>
> >> WSGIDaemonProcess mysite user=intrack group=intrack
> >> python-path=/home/intrack/intrack_pythonenv/lib/pyt
ket file /etc/httpd/logs/wsgi.19713.0.1.sock
does exist hence has been created.
-Alen
On Apr 15, 11:17 pm, Graham Dumpleton
wrote:
> 2009/4/16 Alen Ribic :
>
>
>
> > Thank you Graham for your reply.
>
> > You are definitely right about the permissions.
> > Apache Us
;intrack' user. By the way, /home/intrack has
the django app and the python virtual environment.)
I started the httpd service as root by the way.
Is perhaps the WSGIDaemonProcess not using the intrack user to run the
python process?
-Alen
On Apr 15, 12:35 pm, Graham Dumpleton
wrote:
> 2
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.
Here is the wsgi script:
intrack.wsgi
