> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Brook Hurd > Sent: Monday, February 27, 2006 6:22 PM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] Problems with RPM install > > The RPM install of Nagios was fairly strait forward. I installed the RPMs > for Nagios and the Nagios-plugins along with the misc. required RPMs. > Unfortunately, all the documentation is written toward a non rpm install. >
Not too surprising since RPM installs can vary quite a bit depending on the packager. > The RPM file added all the appropriate httpd.conf configurations, and I > setup up proper users, etc. It is viewable at: > > [link] <http://server.brookhurd.com/nagios/> > > userid: guest > password: guest Results in Internal Server error. I don't know what your OS is but this could be SELinux restrictions if you haven't allowed the proper context for the Nagios sbin directory. > > [EMAIL PROTECTED] nagios]# /etc/rc.d/init.d/nagios start > Starting network monitor: nagios > CONFIG ERROR! Start aborted. Check your Nagios configuration. > [EMAIL PROTECTED] nagios]# > > I just cannot get it to run and cannot see the issue with the Nagios > config. Run /path/to/nagios -v /path/to/nagios.cfg. Nagios will verify your configuration files and report any errors. > I even altered ownership info in the 'nagios.conf' to root: What is the contents of this file? There isn't a nagios.conf that's part of the standard distribution. -- Marc ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null