Hi,

I'm trying to run nagios 2.4 (latest) on Fedora Core 5, and I've installed it with yum. I have SELinux active, and I have the following situation:

The nagios service is running, so I go to http://localhost/nagios/ and I enter my password and the site is shown. But when I try to enter on any of the cgi's the following message is shown:

Whoops!

Error: Could not read object configuration data!

Here are some things you should check in order to resolve this error:

  1. Verify configuration options using the -v command-line option to check for errors.
  2. Check the Nagios log file for messages relating to startup or status data errors.
  3. Make sure you've compiled the main program and the CGIs to use the same object data storage options (i.e. default text file or template-based file).

Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.


I have checked the configuration with "nagios -v" and it looks fine. I disabled SELinux for a second and everything works fine. I tried then to find out what SELinux rule is blocking the access to the files but couldn't find any log where this is notice. I don't want to disable SELinux, i just want to disable the rule affecting nagios. I would appreciate any advice you could give me. Thanks!

MFC

Nagios version: 2.4
OS: Red Hat Fedora Core 5
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to