On 02 Nov 2010, at 4:57 PM, Mohammed Alli wrote: > Hmm, strange one. It does find the file because it shows the message > details, headers and so on.
Those are pulled from the DB not from the filesystem > It's just when I try to preview it, it > gives me the error that the page cannot be found. I've change the perm > on the file to all but still the same problem. The perms are not usually the file itself, the directories above it all need to allow access to the web server user. > Also, nginx is setup to > use www-data as it's user, this was done by default. I've checked my > logs and it's showing this: > > 192.168.0.xxx - - [02/Nov/2010:09:49:27 -0400] "GET > /messages/preview/B58AA24164.A9C39/ HTTP/1.1" 404 237 > "http://192.168.0.ccc/messages/view/B58AA24164.A9C39/"; "Mozilla/5.0 > (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.15) Gecko/20101026 > AskTbUT2V5/3.9.1.14019 Firefox/3.5.15" Please verify that the user has access to the file by suing to the user then try read the file, if you can read the file then the other issue could be the hostname field in the database not corresponding to the actual hostname of the machine. Baruwa will use this field to determine if the message is on the local machine or on a remote machine. > > I've verified that the file does exist and that the user/group has > permission to read it. The check the hostname issue mentioned above. -- JAVA - write once, crawl anywhere. _______________________________________________ Baruwa mailing list [email protected] http://lists.baruwa.org/mailman/listinfo/baruwa
