Problem with Nagios after Nagios XI 2009R1.4B installation

[niebais]

We're running version Nagios XI 2009R1.4B on a CentOS 5.5 fully patched system. We just upgraded to it and noticed when we go to the notifications area and reports we see the following error:
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.

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.

nagios -v doesn't report any errors. There's only 1 instance of nagios running and there are no startup errors or messages in the logs. I think it has to do with a DB username/password changing on the upgrade.

could I get some help fixing the issue.

[mguthrie]

We fixed a bug in the backend credentials with this release, that could be part of the issue. I would update your security credentials from the Admin->Reset Security Credentials page, and also restart the Nagios service. Let us know if that does the trick.

[niebais]

I did that already, and it didn't fix it. What else can I try?

[mguthrie]

The reports screen accesses the Core interface, so my guess is that the problem lies with the nagios monitoring engine itself.

What kind of output do you get from the following items run from the command line?

killall nagios
service nagios start


If the above fails, run:
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
and look for errors. If there are errors from this you'll have to correct them from the Core Config Manager.

[niebais]

I ran the /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg command and there were no errors, plus we have two normal warning we've had forever.

I just stopped and started everything and it didn't fix.

[niebais]

Do you know what table it's trying to read? Is it possible that the table is corrupt or broken? I checked all the mysql username and password logins and they seem ok (read out of the config.inc.php file).

[mguthrie]

Hmm, you have any special configurations on your system like SSL, or a proxy?

You may have already done this, but can you run the following script:

Code: Select all

/usr/local/nagiosxi/scripts/reset_config_perms

[niebais]

Here's the output...the problem still is there.

[*****@***** ~]$ sudo /usr/local/nagiosxi/scripts/reset_config_perms
[sudo] password for ********:
SETUID ROOT OK
RESETTING PERMS

[niebais]

One more thing. I can't acknowledge alerts.

[mguthrie]

I have a few questions, lets see if we can narrow this down.

1. What version did you upgrade from?

2. The system commands (acknowledgements) are still passed through Nagios core, which seems to be the source of this issue. Does the monitoring engine appear to be running?

3. Can you try accessing the Core interface directly? http://<yourserver>/nagios. Do you get the same results?

4. Do your checks appear to be updating and getting fresh results in XI?