Page 1 of 1

Nagios 3.2 www issue after upgrade

Posted: Wed Sep 07, 2011 10:18 am
by arkay
I'm running OpenSuse and just upgraded the OS to 11.4 and the Nagios Core to 3.2. Everything is working just fine after the upgrade - in that I'm getting eMail notifications of service issues, and the nagios -v reports all the config files as being properly configured.

however ...

When I pull up the web interface and attempt to look at hosts or services I get the "Ooops" Unable to read the host and service status information.

When I go down to the configuration menu I can view all of the configuration settings for hosts and services (For everything really)

I've checked all the config files as well as the apache configuration and everything looks good.

I'm completely at a loss for where to look for this bug.

Please help ...

Re: Nagios 3.2 www issue after upgrade

Posted: Wed Sep 07, 2011 4:54 pm
by mguthrie
The browser displays that message when it can't find the status.dat file, which will only exist if Nagios is running. Verify the directory location of that file now that your system is upgraded, as well as the permissions, and double check that Nagios is running.

Re: Nagios 3.2 www issue after upgrade

Posted: Thu Sep 08, 2011 2:32 pm
by arkay
I found the file in /var/lib/nagios - the file is there, but completely empty.

There is also a nagios.log file in that folder, but I'm not sure why - the active log file is in /var/log/nagios.
In that log file there are a bunch of errors which support the idea that there is a permission issue or a configuration issue.

So the follow up quesitons are:
1. How can I know for sure if the status.dat file in the /var/lib/nagios folder is the correct one?
2. How do I verify where both nagios and apahce are looking to find the status.dat?
3. What permissions should I set on the file assuming that this one is correct - I have both the nagios and nagwww groups created.

Randy