Nagios Support Forum

Hello-

I ran some regular updates via yum that the system notified me about - via process I run in Webmin for my NagiosXI box. Now my nagios system won't start.

when I run /usr/local/nagios/bin/nagios -v /usr/local/nagios.cfg

I get that it can't open the main configuration file. Error processing the main config file. I checked the file and opened it with gedit and the file reads fine. I've got several other cfg files in that directory that have recent edit dates of the last 30-40 days. My nagios.cfg file hasn't been edited for over a month. Why can't it be read now?

The web interface to http://servername/nagiosxi starts up and runs fine - just not getting any checks.

Some of the updates were kernel updates and httpd updates to the latest apache release.

I know - someone will probably rail on me for running any updates....but there it is.

How do I get the nagios service to start back up now?

thx

standalone dedicated box
CentOS 5.5 32bit
NagiosXI 2009R1.2D

when I run /usr/local/nagios/bin/nagios -v /usr/local/nagios.cfg

I get that it can't open the main configuration file

First things first: The path to the main configuration file should be /usr/local/nagios/etc/nagios.cfg rather than /usr/local/nagios.cfg. Could you try your verify command again with that and let us know the output once you have the right path?

Another thing you can try if that all checks out is to make sure there are no Nagios processes running, and run it in attached (non-daemon) mode by just removing the -v and seeing if any errors print out there.

Well, as much as I thought I had double checked my file path - apparently I had it wrong. Now running the -v tells me that I had a problem with the hostgroups.cfg file and a listing was not valid. I edited it by hand and tried the -v again and it said everything checked out so I started up nagios and it looks like it's ok.

I was figuring someone would yell at me for doing a kernel PAE update.

Now....do I want to look at release 1.3 yet? Or just leave things alone for a while?

thanks for your quick response Tony

eh, kernel updates are often necessary for security, so I normally do them. I know some people are of the "don't fix it, even if it is broken" mentality, but hey.

As far as 1.3, your best bet would be to make a copy of your current setup (really easy if you're using the VM), and upgrade the copy as a test environment to see how things go before messing with the real one.