Host Check without prior Service Failure ??

[Brian Snead]

I try to determine the cause of each of our alerts and I think I understand how they are supposed to work. A service fails and the host is checked. If it is down, a host down alarm is triggered. If the host is up, a service alarm should be triggered.

But often, I see in the event log just a host failing up to the max checks I have set at 5. Then the service is set to down hard. A host down alarm is triggered. 

Why would the host be checked unless the event log showed a Non-OK service check?

Any ideas?


Here is a section of the log file:

[08-19-2003 07:32:35] SERVICE ALERT: WSSC_SENWIN01;Check for SNMP Services;UNKNOWN;HARD;1;SNMP problem - No data recieved from host
[08-19-2003 07:30:25] SERVICE ALERT: WSSC_SENWIN01;Generic Ping Response;CRITICAL;HARD;1;PING CRITICAL - Packet loss = 100%
[08-19-2003 07:30:25] HOST ALERT: WSSC_SENWIN01;DOWN;HARD;5;CRITICAL - Plugin timed out after 10 seconds
[08-19-2003 07:30:15] HOST ALERT: WSSC_SENWIN01;DOWN;SOFT;4;CRITICAL - Plugin timed out after 10 seconds
[08-19-2003 07:30:05] HOST ALERT: WSSC_SENWIN01;DOWN;SOFT;3;CRITICAL - Plugin timed out after 10 seconds
[08-19-2003 07:29:55] HOST ALERT: WSSC_SENWIN01;DOWN;SOFT;2;CRITICAL - Plugin timed out after 10 seconds
[08-19-2003 07:29:45] HOST ALERT: WSSC_SENWIN01;DOWN;SOFT;1;CRITICAL - Plugin timed out after 10 seconds

There are no prior entries for this host or service.


Thank you,

Brian.


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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