Yet another update ... I turned off SELinux and that seemed to solve the problem. It seems the problem isn't the change from 0.10.4 o 0.10.5 but the change from Fedora 7 to Fedora 9.
Has SELinux ever been beneficial to anyone ever? :) That being said, I'd still like to have it turned on. Given my setup overview, can anyone think of what would be the difference between Fedora 7 and 9 to cause this problem? The only thing I can think of is the stuff that is served out of htdocs as it doesn't have the selinux httpd label. On Thu, Sep 4, 2008 at 7:12 PM, Robert J. Carr <[EMAIL PROTECTED]> wrote: > Hey Graham- > > Thanks so much for the response. Here are some notes: > >> Probably because you restarted Apache using: >> >> sudo /usr/sbin/apachectl start >> >> or similar, instead of: >> >> sudo -H /usr/sbin/apachectl start > > Neither, I always use /etc/init.d/httpd start|stop and always as root > (not sudo). Anything enlightening with this new information? > >> problems at times because things might appear to work, but when box >> reboots and Apache started as root, without those parts of the user >> environment application may fail. > > That's exactly why I always use /etc/init.d because that's what is > used when the system starts. > >> The error is still misleading as Apache will switch to run as Apache >> user. In doing that though, some parts of the environment may still >> reflect that Apache was originally started as root. >> >> Any file permissions must be such that Apache user has read/write >> access as appropriate, not root. > > This is how it is, apache has ownership and read/write access. I only > changed it to root to see if it made a difference, which it didn't. > >> What you may be better off doing is run Apache/mod_wsgi rather than >> mod_python. For that you can use daemon mode of mod_wsgi and have >> daemon process running Trac run as non root, not Apache user, ie., >> normal user account. > > OK, I will try other methods. I should mention, again, that I have > another server setup in as exactly the same way as possible and there > are no problems with it. > > One new piece of information ... I get the same error (ISE 500) > regardless of the resource I request, e.g., if I request an image (in > htdocs) that should be available I get the same exact thing. > > Thanks again for the help. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
