Nagios displaying no results

[Swati Srivastava]

Hello!

I had configured nagios as a daemon process and it was running fine.
Yesterday, it started giving the error - There doesn't appear to be any 
service status information in the status log...
Make sure that Nagios is running and that you have specified the location of 
you status log correctly in the configuration files.

The probem found was that the disk was full. That problem got sorted out and 
Nagios started running fine again this morning.
Again the "disk full" problem came up this afternoon. Which was sorted out 
and the system was rebooted. After that, the same error is coming again - 
There doesn't appear to be any service status information in the status 
log...
Make sure that Nagios is running and that you have specified the location of 
you status log correctly in the configuration files.

I tried restarting nagios, but that didnt help.
on doing ps -aux | grep nagios, it shows the usual display of nagios 
running.
on doing /etc/rc.d/init.d/nagios status, it shows nagios running.
on doing ./check_nagios, it shows located 1 process, status log updated 
....secs ago.

its seems there is some problem with the status log file coz everytime i do 
check_nagios, the time of updation appears same.

How can i sort this problem?
Kindly help me out,
Thanks in advance,
Swati

_________________________________________________________________
Pay Cash on delivery on lakhs of products. 
http://go.msnserver.com/IN/50757.asp Only on Baazee.com



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null