Results 1 to 9 of 9
  1. #1

    HELP ME PLEASE!!! Suexec problem...

    I have been working on this since last night and I am getting very frustrated. Here is my problem. I am trying to use apache/php with suexec. I have my httpd.conf file set-up for a virtualsite and I am using the user and group directives to tell it what uid and gid to run the site as. I also made sure that all of the files are owned by that same uid/gid. In the error_log I get the following:

    [notice] suEXEC mechanism enabled (wrapper: /etc/httpd/bin/suexec)
    [notice] Accept mutex: sysvsem (Default: sysvsem)

    which tells me it is starting, but when I try to access the site I get 403 Forbidden. Of course I go to look in the suexec_log file for information as to why this is happening and the file is not there. So with no information I am having a very hard time troubleshooting this. Any help or suggestions would be appreciated.

  2. #2
    Join Date
    Oct 2001
    Location
    Ann Arbor, MI U.S.A.
    Posts
    217
    I'd check your directory permissions. 403's can creep up for a variety of reasons and it sounds like apache can't even get around to running your cgi because of other errors. This would explain why there's nothing in your suexec_log. I'd check your error log, directory perms and allow/deny lists in apache for the problem. Paste the error_log entries here if you need more help.

    Chris
    Chris Wells [clwells - at - nexcess.net]
    Nexcess - Beyond Hosting
    Dearborn, MI DC ● Southfield, MI DC
    Wordpress Hosting, Magento Hosting & More!

  3. #3
    Thanks for the quick reply. Its not just a cgi I get it on just / and also on /index.php. There is nothing in the error_log that can help me. Also the httpd.conf file is the standard one, except for the virtualsite I added. Is there anything I should check in the standard httpd.conf that might be causing this? Thanks again.

  4. #4
    Join Date
    Oct 2001
    Location
    Ann Arbor, MI U.S.A.
    Posts
    217
    Mike,

    There almost has to be something in the error log like "configuration forbids <ip address> on '/'" or something like that. It sounds to me like directory permissions and/or allow/deny list issues in your httpd.conf. Make all of your dirs leading up to your web root 711 and see if that fixes it. Make all of your php content page 644 for now and see if that helps, this will help us in debugging the matter.

    btw, you can set your apache log level to a little more verbose level by changing the 'LogLevel' line in the httpd.conf to 'LogLevel debug'.

    Chris
    Chris Wells [clwells - at - nexcess.net]
    Nexcess - Beyond Hosting
    Dearborn, MI DC ● Southfield, MI DC
    Wordpress Hosting, Magento Hosting & More!

  5. #5
    I did what you suggested changing the perms did nothing, and changing the log level to debug did not provide anything new either.

  6. #6
    Join Date
    Oct 2001
    Location
    Ann Arbor, MI U.S.A.
    Posts
    217
    Mike,

    Apache logs nothing about the request in the error log? Did you restart apache after making the change? With the loglevel I specified you should get at least some output in the logs regarding the failed request.

    Chris
    Chris Wells [clwells - at - nexcess.net]
    Nexcess - Beyond Hosting
    Dearborn, MI DC ● Southfield, MI DC
    Wordpress Hosting, Magento Hosting & More!

  7. #7
    It logs the request but that's it. Only helpful information is the return code 403 but I got that info by trying to hit the page.

  8. #8
    Join Date
    Oct 2001
    Location
    Ann Arbor, MI U.S.A.
    Posts
    217
    can you hit the page again and then paste the last 5 entires of both teh access and error logs in a new post.

    Thanks,

    Chirs
    Chris Wells [clwells - at - nexcess.net]
    Nexcess - Beyond Hosting
    Dearborn, MI DC ● Southfield, MI DC
    Wordpress Hosting, Magento Hosting & More!

  9. #9
    Join Date
    Dec 2000
    Location
    San Diego, CA
    Posts
    1,571
    Make sure your home directory is chmodded 711 and your public_html directory is 777. Usually anything else but that will cause problems.
    -Mooneer
    Thoughtbug Software: Hosting shouldn't require any thought.
    Legitimate host? Support the Code of Ethical Conduct

Related Posts from theWHIR.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •