check selinux ..... if it is running disable and see ... Szemir On December 29, 2009 12:36:57 am Shawn wrote: > I can't speak much to Perl specifics with Apache - I've never done that. > But, permissions can be tricky. > > If you do have a permissions problem, you *should* be getting a 403 > error, not a 500. But on the off chance we are still dealing with > permissions, check to make sure the web service account has permission > on the parent directory AND that directory's parent. You *may* need to > make sure the service account has some permission right back to root, > though that is rare. > > A 500 error suggests to me that the script itself is faulty. Perhaps > there is something about the runtime environment that is different? > Paths come to mind for that - the PATH for the ROOT user, or regular > user can be different than the PATH for a service account. Or perhaps > there is another environment variable needed, but not set for the > service account? > > I've been bit by both these situations before and they were both a pain > to diagnose... > > Not sure if I helped any, but maybe... :) > > Shawn > > Darcy Brodie wrote: > >>> 755 should give full access to the owner, read and execute to group and > >>> others, so even if the APACHE user does not have ownership, it should > >>> fall under the "other" permissions > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
