Nagios on Plesk Installation Trouble (Apache 403 Forbidden Errors)

Discussion in 'Parallels Plesk Panel for Linux - 8.x and Older' started by orware, May 2, 2008.

  1. orware

    orware New Member

    Hello everyone :).

    Yesterday I naively attempted to install Nagios on a Plesk server running RHEL4 using the Fedora Quickstart instructions available here:

    I skipped the prerequisites step because Plesk already has Apache installed, gcc, gd and the other prerequisites installed.

    In Step 5, Configuring the Web Interface, I held off on the last step which asked to restart Apache, ("service httpd restart").

    I continued all the way until Step 7, started Nagios, and then it was at this point that I restarted Apache.

    I immediately went our main website to see if everything was OK...and unfortunately it wasn't.

    For every page I received a 403 Forbidden Error with the message "You don't have permission to access / on this server" (or whatever other folder I tried to access).

    I checked permissions on the files (in Plesk all httpdocs folders have to belong to the psaserv group and all files and folders within the httpdocs folders need to belong to the psacln group) and everything checked out. The default permissions for the httpdocs folders in Plesk is 750, and the only way I was able to get the sites back up was to change the permissions manually to 751, but that's not a real fix.

    I thought the problem was caused by the nagios.conf file that was added into the conf.d folder, but after I removed that and restarted Apache the problem still persisted.
    Then I stopped the service and tried removing Nagios using the following thread:

    And then I restarted Apache but that didn't seem to work either.

    Then I thought maybe the user/group nagios/nagcmd was causing an issue but after removing those the problem still continued.

    At the moment all I want to do is to remove Nagios completely and get my Plesk setup operating normally again and then I'll continue playing with Nagios (but this time on a Virtual Machine setup, not my production environment like a knucklehead).

    Any help anyone can provide is tremendously appreciated because Plesk support won't touch this since Nagios is not supported by them and I've tried everything I can think of with my somewhat newb Linux background. The main thing at the moment is that the sites are back up (the Plesk server runs a community college website), but the 751 permission fix is klugdy and I'd like to figure out what the real problem actually is.

    Thank you for any assistance you might be able to provide :).
  2. orware

    orware New Member

    Some additional info

    Some additional information:

    The Nagios FAQ article above is supposed to help with machines that are using Suexec. I don't really know whether Plesk is using it or not (running the command to check whether it is on my machine says that it isn't) but within the Plesk folder there is a folder named suexec so I'm wondering if that might be related to the problem.
  3. orware

    orware New Member

    Solution Found

    I ran a search here in the Plesk forums (perhaps I should have done that first) and found the following thread:

    And found a solution to the issue.

    The problem was that Nagios had deleted apache from the psaserv group so the solution was to run:
    usermod -G psaserv apache

    Restart apache using:
    /etc/init.d/httpd restart

    And everything was back in business :)
  4. webpointer

    webpointer New Member

    Thanks for the solution! I had the same problem over here and after putting back apache in the psaserv group everything was back online!

Share This Page