<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> <TITLE></TITLE> <META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD> <BODY> <DIV>no, i think it's this way: service check fails, so host check is done...host check is failed so service NOTIFICATIONS are suppressed, not service CHECKS. as someone mentioned earlier, it's the service check coming back up that puts the host in an up state....i think.</DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Bishop, Dean [mailto:dean.bishop@tcdsb.org] Sent: Thursday, October 10, 2002 2:12 PM To: Jolet, John; 'nagios-users@lists.sourceforge.net' Subject: RE: [Nagios-users] RE: What the... </DIV> <DIV>you know...now that i am paying attention, i don't get many service notifications. Hardly any as a matter of fact. Lots of Host notifications though.</DIV> <DIV> </DIV> <DIV>why would this be? i see services being checked.</DIV> <DIV> </DIV> <DIV>please, someone confirm for me: a service fails, host check is done, host fails, services are no longer checked for that host, so max_check_attempts for the services is never reached, no service notification is sent?</DIV> <DIV> </DIV> <DIV>almost all of my devices are either up or down. very rarely does just a service fail. services currently defined are pretty much just port-23 checks for switches and port 135 checks for windoze servers.</DIV> <DIV> </DIV> <DIV>later,</DIV> <DIV>dean</DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Jolet, John [mailto:John.Jolet@misyshealthcare.com] Sent: Thursday, October 10, 2002 2:30 PM To: 'nagios-users@lists.sourceforge.net' Subject: RE: [Nagios-users] RE: What the... </DIV> <DIV>Can you include the bit of the config that shows the parent-child relationships?</DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----O[Jolet, John] riginal Message----- From: Bishop, Dean [mailto:dean.bishop@tcdsb.org] Sent: Thursday, October 10, 2002 1:14 PM To: Bishop, Dean; 'nagios-users@lists.sourceforge.net' Subject: [Nagios-users] RE: What the... </DIV> First, sorry bout the subject i realize that it is inappropriate. it does, however capture my initial response. We are in the midst of many nightmares concurrently: smoking servers, irreplaceable data lost, network latency, cold lunch, sore finger, you know the whole gambut at once. apologies to all. here is another entry from my logs. Each host is dependant on the previously numbered host (e.g. Marshall-McLuhan-0561SW2A_4-HS7 is the parent of Marshall-McLuhan-0561SW2A_5-HS7 who is the parent of Marshall-McLuhan-0561SW2A_6-HS7, etc. <DIV>why, once Marshall-McLuhan-0561SW2A_14-HS7 is determined to be UNREACHABLE (due to the failure of Marshall-McLuhan-0561SW2A_4-HS7), is the service checked on Marshall-McLuhan-0561SW2A_14-HS7?</DIV> [1034172479] HOST ALERT: Marshall-McLuhan-0561SW2A_14-HS7;DOWN;SOFT;1;CRITICAL - Plugin timed out after 18 seconds [1034172516] HOST ALERT: Marshall-McLuhan-0561SW2A_7-HS7;DOWN;SOFT;1;CRITICAL - Plugin timed out after 18 seconds [1034172552] HOST ALERT: Marshall-McLuhan-0561SW2A_6-HS7;DOWN;SOFT;1;CRITICAL - Plugin timed out after 18 seconds [1034172588] HOST ALERT: Marshall-McLuhan-0561SW2A_5-HS7;DOWN;SOFT;1;CRITICAL - Plugin timed out after 18 seconds [1034172624] HOST ALERT: Marshall-McLuhan-0561SW2A_4-HS7;DOWN;SOFT;1;CRITICAL - Plugin timed out after 18 seconds [1034172644] HOST ALERT: Marshall-McLuhan-0561SW2A_4-HS7;DOWN;HARD;2;CRITICAL - Plugin timed out after 18 seconds [1034172644] HOST NOTIFICATION: nagiosadmin;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 18 seconds [1034172645] HOST NOTIFICATION: Marco;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 18 seconds [1034172645] HOST NOTIFICATION: Kevin-NonCritical;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;notify-by-epager;CRITICAL - Plugin timed out after 18 seconds [1034172645] HOST NOTIFICATION: Kevin;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 18 seconds [1034172646] HOST NOTIFICATION: Keith-NonCritical;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;notify-by-epager;CRITICAL - Plugin timed out after 18 seconds [1034172646] HOST NOTIFICATION: Keith;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 18 seconds [1034172646] HOST NOTIFICATION: Ben;Marshall-McLuhan-0561SW2A_4-HS7;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 18 seconds [1034172647] HOST ALERT: Marshall-McLuhan-0561SW2A_5-HS7;UNREACHABLE;HARD;2;CRITICAL - Plugin timed out after 18 seconds [1034172647] HOST ALERT: Marshall-McLuhan-0561SW2A_6-HS7;UNREACHABLE;HARD;2;CRITICAL - Plugin timed out after 18 seconds [1034172647] HOST ALERT: Marshall-McLuhan-0561SW2A_7-HS7;UNREACHABLE;HARD;2;CRITICAL - Plugin timed out after 18 seconds [1034172647] HOST ALERT: Marshall-McLuhan-0561SW2A_14-HS7;UNREACHABLE;HARD;2;CRITICAL - Plugin timed out after 18 seconds [1034172647] SERVICE ALERT: Marshall-McLuhan-0561SW2A_14-HS7;Port Check-23;CRITICAL;HARD;1;Socket timeout after 10 seconds -----Original Message----- From: Bishop, Dean Sent: Thursday, October 10, 2002 1:04 PM To: 'nagios-users@lists.sourceforge.net' Subject: What the *&#( !! Importance: High Can someone explain this to me?? why in the world is the service for testserver01.tcdsb.org being checked after the host has been determined down? also why is the host being checked before the service?? [root@NMS var]# tail nagios.log -n 3000 |grep testserver01 [1034266896] HOST ALERT: testserver01.tcdsb.org;UP;HARD;1;(Host assumed to be up) [1034266896] SERVICE ALERT: testserver01.tcdsb.org;Misc Servers - Port Check 135;OK;HARD;1;TCP OK - 0 second response time on port 135 [1034267924] HOST ALERT: testserver01.tcdsb.org;DOWN;SOFT;1;CRITICAL - Plugin timed out after 8 seconds [1034267933] HOST ALERT: testserver01.tcdsb.org;DOWN;HARD;2;CRITICAL - Plugin timed out after 8 seconds [1034267933] HOST NOTIFICATION:nagiosadmin;testserver01.tcdsb.org;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 8 seconds [1034267934] HOST NOTIFICATION:Keith;testserver01.tcdsb.org;DOWN;host-notify-by-email;CRITICAL - Plugin timed out after 8 seconds [1034267934] SERVICE ALERT: testserver01.tcdsb.org;Misc Servers - Port Check 135;CRITICAL;HARD;1;Socket timeout after 2 seconds [1034268938] HOST ALERT: testserver01.tcdsb.org;UP;HARD;1;PING OK - Packet loss = 0%, RTA = 0.61 ms [1034268938] HOST NOTIFICATION:nagiosadmin;testserver01.tcdsb.org;UP;host-notify-by-email;PING OK - Packet loss = 0%, RTA = 0.61 ms [1034268938] HOST NOTIFICATION:Keith;testserver01.tcdsb.org;UP;host-notify-by-email;PING OK - Packet loss = 0%, RTA = 0.61 ms [1034268938] SERVICE ALERT: testserver01.tcdsb.org;Misc Servers - Port Check 135;OK;HARD;1;TCP OK - 0 second response time on port 135 [root@NMS var]# </BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>