|
From: Ben W. <Ben...@co...> - 2004-04-21 19:28:24
|
Greetings all, I had a problem this morning where a host was down but I received a service notification. I have disabled host notifications altogether but I don't want to know about a service being unavailable if a host is down. Below is from the Alert History. [04-21-2004 06:21:11] SERVICE ALERT: host-xxx;load;CRITICAL;HARD;1;CHECK_NRPE: Socket timeout after 10 seconds. [04-21-2004 06:20:50] SERVICE ALERT: host-xxx;httpd processes;CRITICAL;HARD;1;Connection refused by host \/ HOST DOWN ALERT HERE \/ [04-21-2004 06:20:50] HOST ALERT: host-xxx;DOWN;HARD;6;PING CRITICAL - Packet loss = 100% <-- GOT NOTIFIED HERE --> [04-21-2004 06:17:55] SERVICE ALERT: host-xxx;Load Combo check;CRITICAL;HARD;1;COMBO Connection refused by host - Connection refused by host - Connection refused by host - Connection refused by host - Connection refused by host - Connection refused by host - Connection refused by host - Is there a setting I missed that will make sure the host is up before notifying about service problems? Regards, Ben |