On Mon, Sep 27, 2010 at 9:31 AM, Carl Nobile <[email protected]> wrote: > > The error you mentioned above is caused by one of two reasons. > > 1) The settings.py path was never defined in your wsgi file. > 2) the settings.py file itself is broken and cannot be loaded even if > the path to it is correct. > > The first is easy to fix just add something like this to your wsgi file: > > import os > > os.environ['DJANGO_SETTINGS_MODULE'] = path.settings
I do have os imported in the settings.py and as mentioned, DJANGO_SETTINGS_MODULE has been specified in the django.wsgo file: os.environ['DJANGO_SETTINGS_MODULE'] = 'blog.settings' blog is the name of my django project. > The second problem can be debuged by trying to load the settings file > in the python interpreter manually and track the error from there. I just executed python -v settings.py and no error was presented. My PYTHON_PATH is just fine though, I'm concerned about the www-user though. I don't know how to specify the sys.path for it, but I was thinking mod_wsgi should take care of this. > ~Carl > > On Mon, Sep 27, 2010 at 9:18 AM, safar objorn <[email protected]> wrote: > > I know this isn't safe, but I haven't setup groups yet for the www-admin > > user, I just gave everything in my /home/safar/sites/public/ directory 777 > > privileges. Also, /home/ehath/sites/public/blog/ should be > > /home/safar/sites/public/blog/, but either way, it doesn't affect anything. > > > > On Mon, Sep 27, 2010 at 8:11 AM, safar objorn <[email protected]> > > wrote: > >> > >> I've searched the logs from the mailing list, I went three pages deep > >> before deciding to ask for help. It seems there are several other people > >> who > >> have experienced this, and I don't want to think mine is any different, but > >> I'm not seeing the solution, and I'm hoping someone here can help me. > >> > >> This is the error when retrieving attempting to retrieve the page: > >> > >> " > >> (500) Internal Server Error > >> > >> The server encountered an internal error or misconfiguration and was > >> unable to complete your request. > >> > >> Please contact the server administrator, [no address given] and inform > >> them of the time the error occurred, and anything you might have done that > >> may have caused the error. > >> > >> More information about this error may be available in the server error > >> log. > >> " > >> > >> > >> This is the error given by /var/log/apache2/error.log: > >> > >> " > >> [Mon Sep 27 07:54:23 2010] [error] [client 127.0.0.1] raise > >> ImportError, "Could not import settings '%s' (Is it on sys.path? Does it > >> have syntax errors?): %s" % (self.SETTINGS_MODULE, e) > >> [Mon Sep 27 07:54:23 2010] [error] [client 127.0.0.1] ImportError: Could > >> not import settings 'blog.settings' (Is it on sys.path? Does it have syntax > >> errors?): No module named blog.settings > >> " > >> > >> > >> This is the contents of my /home/safar/sites/public/blog/apache.py file: > >> > >> " > >> import os, sys > >> > >> sys.path.append('/home/safar/sites/public') > >> os.environ['DJANGO_SETTINGS_MODULE'] = 'blog.settings' > >> import django.core.handlers.wsgi > >> application = django.core.handlers.wsgi.WSGIHandler() > >> " > >> > >> > >> Contents of my /etc/apache2/sites-available-default file: > >> > >> " > >> <VirtualHost *:80> > >> > >> SetEnv PYTHON_PATH /home/safar/sites/public/ > >> > >> WSGIScriptAlias / /home/safar/sites/public/blog/apache/django.wsgi > >> > >> Alias /media/ /home/safar/sites/public/blog/media/ > >> > >> <Directory /home/ehath/sites/public/blog/> > >> Order deny,allow > >> Allow from all > >> </Directory> > >> > >> <Directory /home/safar/sites/public/blog/media/> > >> Order deny,allow > >> Allow from all > >> </Directory> > >> > >> <Directory /home/safar/sites/public/blog/apache> > >> Order deny,allow > >> Allow from all > >> </Directory> > >> > >> </VirtualHost> > >> " > >> > >> I wasn't so sure the <Directory /home/ehath/sites/public/blog/> was > >> necessary but I put it in just because nothing else was working, it > >> obviously didn't help. Also, I don't think the SetEnv PYTHON_PATH even does > >> anything, I was confused when I put that in, I don't think it's necessary > >> either since mod_wsgi can specify this. I've removed both and it still > >> doesn't work. I hope someone can helpl, and thank you for your time. > > > > -- > > 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. > > > > > > -- > ------------------------------------------------------------------------------- > Carl J. Nobile (Software Engineer) > [email protected] > ------------------------------------------------------------------------------- > > -- > 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.
