ansaurus

Question

Answer 1

A:

First, try setting the group-sticky bit on the directories:

find /home/website -type d -exec chmod g+s {} \;

Then the perms should read rwxrws---. See if this makes a difference.

If that fails, you can try to poke around as the "website" user and see what happens. Temporarily give the user "website" a home directory (not /home/website, it needs to be something else, like /var/home/website), password, and login shell, then use su - website to switch to it. Try listing the contents of /home/website and try reading files in there. Fix any problems.

Hope this helps.

P.S. I'm assuming /var/log/apache/access_log (or maybe it's /var/log/http/access_log) doesn't have anything useful.

Mike DeSimone 2010-04-21 23:28:14

the sticky bit did it. thanks.

Kevin 2010-04-21 23:50:14

IIRC, without the sticky bit, apache tries to access the directory as group "apache", which is the (default) group that executed the server. The sticky bit tells the OS to use the directory's group in that directory instead.

Mike DeSimone 2010-04-21 23:52:41

The sticky bit should only apply when writing files to the directory not read files from directory.

Graham Dumpleton 2010-04-22 01:40:49

Makes me wonder if mod_wsgi is trying to write to the directory. ... But are you sure, since you have to have execute permission on a directory to read its contents?

Mike DeSimone 2010-04-22 04:27:36

I'm not sure exactly what's going on. Before I did g+s, the permissions had to be rwxrwxr-x to prevent a 403 error. After g+s, rwxrwx--- works ok. The owner of everything is website:django, where django:x:505:apache,website. I had previously tried setting the owner to website:apache with no luck.

Kevin 2010-04-22 20:02:02

ansaurus

tags:

views:

answers:

django/apache permissions problem

related questions