Error: Host Status Information Not Found

[Marc Powell]

I'll bet even money you have multiple copies of Nagios running. Stop the
service then use ps to see. If you do, kill the others and restart
Nagios.

--
Marc

> -----Original Message-----
> From: Serveur-Faucon Surveillance [mailto:SrvFaucon at cslaval.qc.ca]
> Sent: Tuesday, April 29, 2003 12:29 PM
> To: nagios-users at lists.sourceforge.net
> 
> Hi all,
> 
> I have installed Nagios v1.0 on a RedHat 8 server and everything was
> working right in my tests with about 10 hosts and 30 services. So I
began
> to add a couple of hosts and services, up to 84 hosts and 117
services.
> 
> The thing is, when I clic on "service detail" I get sometimes 84h/117s
or
> 52h/85s or 17h/50s. On top of that, when I clic on the lasts services
or
> hosts that I added I get the errors "Error: Service Status Not Found!"
or
> "Error: Host Status Information Not Found".
> 
> So I think :"mabe I need to wait for a day so that the logs rotate,
but I
> did wait 2 days and thinking about it host status and service status
are
> live.
> 
> Is there someone out there with some idears? Thanks.
> 
> Alex
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> 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


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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