Nagios initial Config problems


Hello All,

I am installing Nagios for the first time on a Slack box and am having some troubles. I have gotten to the point where the Nagios is installed, apache is running and I can even open a web browser and point to the server and get the Nagios main screen. I can even open up a few links such as the event log, alert summary and notifications.

However, when I try to click on the tactical overview link I get the following:


Error: Could not read host and service status information!

The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running. If Nagios is indeed not running, this is a normal error message. It simply indicates that the CGIs could not obtain the current status of hosts and services that are being monitored. If you’ve just installed things, make sure you read the documentation on starting Nagios.

Some other things you should check in order to resolve this error include:

  1. Check the Nagios log file for messages relating to startup or status data errors.
  2. Always verify configuration options using the -v command-line option before starting or restarting Nagios!

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 *

I’m sure most people have seen this and I am wondering if it is a ‘linking’ problem. Whereas, apache cannot read those file because it does not know where they are?

Thanks in advance,


I thought all the CGI scrpits where in one place, i.e. the same place as showlog.cgi and the like, which you mention are accessible, and as such would tend not to think that apache has a problem linking to the CGI scripts…
I’m not trying to ask a daft question here, but I take it that the nagios process is running and that you don’t in fact see anything noteworthy in the log file or when performing the verify command?


Yea, I used the verify and it came back with no errors. I had some errors with hostname and loopback originally but those were cleared.

I’m not sure why it will pull some cgi(s) and not others and yes they are pulling from the same directory.



Assuming you have your object definitions grouped in seperate configuration files, you could comment a bunch of them out of nagios.cfg and just leave, say, one file in to start with. Verify and restart nagios and hopefully you should get something, then slowly add in the rest of your files and see when it goes awry to deduce the config file within which the problem may lie… If it still complains with only one object configuration file then there’s a wider issue that needs resolving.

Also, make sure your permissions on the object configuration files are correct, e.g.
-rw-rw-r-- 1 nagios nagios 3293 Feb 5 16:43 switch.cfg