Nagios Support Forum

Hi I am getting an error in Nagios server . When I go to Reports --> Click on availability report --> gives the following error:

Whoops!

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 http://www.nagios.org.



Please Guide ASAP as this is a critical issue

Regards,
Renuka

I am unable to configure new clients because of this issue , Please do the need full ASAP.

I have checked the nagios status .. it is stopped plz see th ebelow steps which i have performed

1. [root@ZUE-V-G0000004 /]# service nagios status
No lock file found in /usr/local/nagios/var/nagios.lock

2. Created the Nagios lock file manually with no data

[root@ZUE-V-G0000004 var]# vi nagios.lock

3. [root@ZUE-V-G0000004 /]# service nagios start
Starting nagios:CONFIG ERROR! Start aborted. Check your Nagios configuration.


Please let me know how should i start it manually

try /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg and try to pinpoint your error in the config. That might solve your issue. Probably you have a config error which makes nagios unable to restart. My 2 cents that if your config is fixed you won't have any issues anymore.

Yeah, MathieuS suggested a very good idea. Run his command:
And read its output very closely. It will tell you what config files have what errors and will give you an approximation of what line they exist on. If you have trouble finding the error, post the output of that command here and we'll give you a hand.