Are you running on a Linux system with SELinux enabled? Graham
On 31 March 2011 10:53, Fred <[email protected]> wrote: > Thanks for looking at this. here's the info you requested plus a > bunch more just in case. > > [root@daffyduck www]# ls -las /home/djangodeploy > total 12 > 4 drwxrwxrwx. 3 apache apache 4096 Mar 30 19:27 . > 4 drwxrwxrwx. 7 root root 4096 Mar 30 19:28 .. > 4 dr-xr-xr-x. 4 apache apache 4096 Mar 30 19:34 HWdj > 0 -rwxrwxrwx. 1 apache apache 0 Mar 30 10:40 __init__.py > > [root@daffyduck www]# ls -las /home/djangodeploy/*/settings.py > 4 -r--r--r--. 1 apache apache 3198 Feb 20 09:45 /home/djangodeploy/ > HWdj/settings.py > > I've been trying various permutations/combinations; so just in case > I've messed up something else, here's the current contents of the key > files > > ---------------------wsgi.conf------------------------------------- > LoadModule wsgi_module modules/mod_wsgi.so > > #WSGIScriptAlias /myapp /var/www/wsgi-scripts/myapp.wsgi > WSGIScriptAlias /wsgi /var/www/wsgi-scripts > WSGIPythonPath /home/djangodeploy > #WSGIDaemonProcess sunbelt.org processes=2 threads=15 python-path=/ > home/djangodeploy > #WSGIProcessGroup sunbelt.org > LogLevel info > WSGISocketPrefix /var/run/wsgi > > <Directory /var/www/wsgi-scripts> > Order allow,deny > Allow from all > </Directory> > > <Directory /home/djangodeploy> > Order allow,deny > Allow from all > </Directory> > > > -----------------------------and /var/www/wsgi-scripts/ > test3.wsgi------------------------------ > import sys, os > sys.path.insert(0, '/home/djangodeploy/HWdj') > print >>sys.stderr, '\n\n', sys.path > import settings > import django.core.management > django.core.management.setup_environ(settings) > utility = django.core.management.ManagementUtility() > command = utility.fetch_command('runserver') > command.validate() > import django.conf > import django.utils > django.utils.translation.activate(django.conf.settings.LANGUAGE_CODE) > import django.core.handlers.wsgi > application = django.core.handlers.wsgi.WSGIHandler() > > > --------------------and the output of the apache error_log > is---------------------------------- > [Wed Mar 30 19:50:14 2011] [error] ['/home/djangodeploy/HWdj', '/home/ > djangodeploy', '/usr/lib/python26.zip', '/usr/lib/python2.6', '/usr/ > lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/ > python2.6/lib-old', '/usr/lib/python2.6/lib-dynload', '/usr/lib/ > python2.6/site-packages', '/usr/lib/python2.6/site-packages/gst-0.10', > '/usr/lib/python2.6/site-packages/gtk-2.0', '/usr/lib/python2.6/site- > packages/webkit-1.0'] > [Wed Mar 30 19:50:14 2011] [error] [client 192.168.218.34] mod_wsgi > (pid=4008): Target WSGI script '/var/www/wsgi-scripts/test3.wsgi' > cannot be loaded as Python module. > [Wed Mar 30 19:50:14 2011] [error] [client 192.168.218.34] mod_wsgi > (pid=4008): Exception occurred processing WSGI script '/var/www/wsgi- > scripts/test3.wsgi'. > [Wed Mar 30 19:50:14 2011] [error] [client 192.168.218.34] Traceback > (most recent call last): > [Wed Mar 30 19:50:14 2011] [error] [client 192.168.218.34] File "/ > var/www/wsgi-scripts/test3.wsgi", line 6, in <module> > [Wed Mar 30 19:50:14 2011] [error] [client 192.168.218.34] import > settings > [Wed Mar 30 19:50:14 2011] [error] [client 192.168.218.34] > ImportError: No module named settings > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
