Nagios Support Forum

mguthrie wrote: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?

I. just upgraded from the previous version 1.4A I think or whatever your stable release was.
2. According to a ps -ef | grep -i nagios
nagios 6984 5076 0 10:55 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
Also we have 4 green arrows at the top indicating everything is ok. Nagios is checking for alerts, etc.
3. Interesting thing in the core interface, everything I click on gets the error, but it does allow me to log in

4. The checks seem to be getting fresh results. We've had several monitors go up and down today.

If you haven't already, can you try restarting the server? The Core interface is behaving as if the monitoring engine is not running, or the main config files are not readable by it. The only cause I can think of would be multiple nagios instances, but if you've already run the killall nagios, then service nagios start, I'm not sure what else it would be. Strange....

mguthrie wrote:If you haven't already, can you try restarting the server? The Core interface is behaving as if the monitoring engine is not running, or the main config files are not readable by it. The only cause I can think of would be multiple nagios instances, but if you've already run the killall nagios, then service nagios start, I'm not sure what else it would be. Strange....

Yeah I didn't think a server reboot would do it, but I did it anyway and we still have the same problem. What else could we do? I'm thinking recompiling the core with the installer might work. What's the best way to recompile the core?

Ok, I found the solution *phew*. My own fat fingering. Here's the error message I was missing:

[1298573703] Warning: Could not open object cache file '/mtn/ram/objects.cache' for writing!

The objects.cache file was put on a ram disk and should have been /mnt/ram. Sorry I didn't notice this error in the logs previously. Thanks for the help! We're back up and running.

It would be nice if the objects.cache file can't be written, Nagios should give a fatal error instead. Thanks for the help again.

Glad you figured it out! *phew* on this end as well I was running out of ideas.