Well, sure enough that shows that all users have write access. But I presume your error message is still talking about a permissions error relating to satchmo.log right? I just looked at my satchmo.log file and I do note that everyone also has execute permission to it. Suppose you may as well try that, too. chmod a+x satchmo.log
--Stuart On Fri, Dec 10, 2010 at 4:20 PM, jc <[email protected]> wrote: > Here it is...sorry about that. > > -rw-r--r-- 1 root root 698043 2010-12-10 14:40 datadump.json > -rw-r--r-- 1 root root 278 2010-12-10 19:47 django.wsgi > drwxr-xr-x 2 root root 4096 2010-12-10 14:40 images > -rw-r--r-- 1 root root 0 2010-12-10 14:40 __init__.py > -rw-r--r-- 1 root root 135 2010-12-10 14:40 __init__.pyc > -rw-r--r-- 1 root root 1725 2010-12-10 14:40 local_settings.py > -rw-r--r-- 1 root root 1614 2010-12-10 14:40 local_settings.pyc > drwxr-xr-x 2 root root 4096 2010-12-10 14:40 localsite > -rwxr-xr-x 1 root root 995 2010-12-10 14:40 manage.py > -rw-rw-rw- 1 root root 64 2010-12-10 22:19 satchmo.log > -rw-r--r-- 1 root root 5614 2010-12-10 14:40 settings.py > -rw-r--r-- 1 root root 4095 2010-12-10 14:40 settings.pyc > -rw-r--r-- 1 root root 537600 2010-12-10 14:40 simple.db > drwxr-xr-x 5 root root 4096 2010-12-10 14:40 static > drwxr-xr-x 4 root root 4096 2010-12-10 14:40 templates > -rw-r--r-- 1 root root 85 2010-12-10 14:40 urls.py > -rw-r--r-- 1 root root 254 2010-12-10 14:40 urls.pyc > > > On Dec 10, 5:19 pm, Stuart Laughlin <[email protected]> wrote: >> Hmm, I don't see a satchmo.log file. Are these the contents of >> /srv/www/gnseagle.org/store/? If so, go ahead and create the >> satchmo.log file (touch satchmo.log) and then chmod a+w the file. >> >> --Stuart >> >> >> >> >> >> >> >> On Fri, Dec 10, 2010 at 4:15 PM, jc <[email protected]> wrote: >> > here is my ls -l store does this look alright? >> >> > -rw-r--r-- 1 root root 698043 2010-12-10 14:40 datadump.json >> > -rw-r--r-- 1 root root 278 2010-12-10 19:47 django.wsgi >> > drwxr-xr-x 2 root root 4096 2010-12-10 14:40 images >> > -rw-r--r-- 1 root root 0 2010-12-10 14:40 __init__.py >> > -rw-r--r-- 1 root root 135 2010-12-10 14:40 __init__.pyc >> > -rw-r--r-- 1 root root 1725 2010-12-10 14:40 local_settings.py >> > -rw-r--r-- 1 root root 1614 2010-12-10 14:40 local_settings.pyc >> > drwxr-xr-x 2 root root 4096 2010-12-10 14:40 localsite >> > -rwxr-xr-x 1 root root 995 2010-12-10 14:40 manage.py >> > -rw-r--r-- 1 root root 5614 2010-12-10 14:40 settings.py >> > -rw-r--r-- 1 root root 4095 2010-12-10 14:40 settings.pyc >> > -rw-r--r-- 1 root root 537600 2010-12-10 14:40 simple.db >> > drwxr-xr-x 5 root root 4096 2010-12-10 14:40 static >> > drwxr-xr-x 4 root root 4096 2010-12-10 14:40 templates >> > -rw-r--r-- 1 root root 85 2010-12-10 14:40 urls.py >> > -rw-r--r-- 1 root root 254 2010-12-10 14:40 urls.pyc >> >> > On Dec 10, 5:07 pm, Stuart Laughlin <[email protected]> wrote: >> >> I'm surprised that didn't fix it; I get this error myself from time to >> >> time, and giving write permissions always clears it up. Did you "ls >> >> -l" your store directory and make sure everyone has write permission >> >> to satchmo.log? Did you restart apache? Maybe I'm barking up the wrong >> >> tree (but I'm not convinced yet). :) >> >> >> --Stuart >> >> >> On Fri, Dec 10, 2010 at 4:01 PM, jc <[email protected]> wrote: >> >> > I went into my project folder and "chmod a+w satchmo.log" just to see >> >> > if it would clear up the error is still showing up. Do I need to do >> >> > anything else after setting permissions for that .log file? I'm >> >> > unfamiliar how or where to set permissions for the www-data file/user. >> >> > Regardless, I changed permission for the satchmo.log file, still >> >> > getting that error. >> >> >> > thanks for the reply back! >> >> > j. >> >> >> > On Dec 10, 4:42 pm, Stuart Laughlin <[email protected]> wrote: >> >> >> You just need to give your web-server user (probably www-data) write >> >> >> access to your logfile. Or do the less ideal thing and give write >> >> >> access to the logfile for everyone, i.e. "chmod a+w >> >> >> /srv/www/gnseagle.org/store/satchmo.log" >> >> >> >> --Stuart >> >> >> >> On Fri, Dec 10, 2010 at 3:27 PM, jc <[email protected]> wrote: >> >> >> > Hi! >> >> >> >> > From what I can tell so far, it had to do with my apache >> >> >> > WSGIScriptAlias (I didn't have one). I looked at the server logs and >> >> >> > pretty much figured that out. Still, after I debugged the app I know >> >> >> > get a web page that just thrashed, the page will not load or >> >> >> > anything. I looked into the logs and it *seems* to have given me a >> >> >> > clue to what it might be. Here is part of the error log that I keep >> >> >> > getting.http://paste.pocoo.org/show/trDqU0WTn17Zhx2PeYwe/ >> >> >> >> > What is causing this? Any help would be greatly appreciated. >> >> >> >> > Thanks, >> >> >> > J. >> >> >> >> > On Dec 10, 3:50 pm, Josh Cartmell <[email protected]> wrote: >> >> >> >> It looks like mod_wsgi isn't actually running so apache is just >> >> >> >> serving >> >> >> >> up your public_html directory. I bet if you put a file called >> >> >> >> index.html in there and put; >> >> >> >> Hello World, in the file you would see Hello World instead of the >> >> >> >> directory listing. You need to look more into your mod_wsgi >> >> >> >> configuration. Are you running in daemon mode? Also, its >> >> >> >> generally a >> >> >> >> bad idea to put django apps inside your public html directory >> >> >> >> because it >> >> >> >> can expose things like your settings.py which contains passwords, >> >> >> >> etc... >> >> >> >> >> -Josh >> >> >> >> >> On 12/10/10 11:21 AM, jc wrote: >> >> >> >> >> > My Apache (mod_wsgi) Django app only lists the files of my >> >> >> >> > website/ >> >> >> >> > project instead of the actual running website/application. My >> >> >> >> > guess is >> >> >> >> > that it's mod_wsgi that is the culprit but I'm not really sure. >> >> >> >> > What >> >> >> >> > are some of the causes of this? Here is a screenshot of what I am >> >> >> >> > seeing instead of my actual web >> >> >> >> > application:http://yfrog.com/j5screenshotgcqp >> >> >> >> >> > thanks, >> >> >> >> > j. >> >> >> >> > -- >> >> >> > You received this message because you are subscribed to the Google >> >> >> > Groups "Satchmo users" 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 >> >> >> > athttp://groups.google.com/group/satchmo-users?hl=en. >> >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups "Satchmo users" 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 >> >> > athttp://groups.google.com/group/satchmo-users?hl=en. >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Satchmo users" 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 >> > athttp://groups.google.com/group/satchmo-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" 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/satchmo-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
