<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> I wonder if there is something you can do with notification escalations? I know you can control how the notifications are sent out, but I don’t know if a state change from down to unreachable to down will cause the escalation to reset.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: Israel Brewster [mailto:israel@frontierflying.com] Sent: Wednesday, April 08, 2009 2:32 PM To: Marc Powell Cc: nagios-users@lists.sourceforge.net Users Subject: Re: [Nagios-users] Children "unreachable" on soft down?<o:p></o:p> </div> </div> <o:p> </o:p> On Apr 8, 2009, at 9:28 AM, Marc Powell wrote: > > On Apr 8, 2009, at 11:44 AM, Israel Brewster wrote: > >> So is this just something I'll have to live with? I don't seem to be >> getting much feedback on the subject. :( > > Well, my response would be to fix the problem that's causing the > outages in the first place or adjust the way you're monitoring the > parents so that the plugin used recognizes when this temporary event > is occurring. Ok, fair enough. There is nothing we can do about the outages (as I explained in one of my e-mail, they are an artifact of the connection type), so that leaves us with adjusting the monitoring. Now I thought that the recheck options were there exactly for this reason: to catch brief outages and not alert. And for the parent host that seems to be the case, but apparently that logic doesn't carry on to the child hosts. As such, somehow things would need to be adjusted so it never even sees the outages, even enough to go into a soft down state. Anyone have any suggestions for how I can accomplish this? Adjusting the timeout or using, say, an ssh check rather than icmp won't do it - the packets are still lost, and the ssh check would still timeout.. Perhaps if I sent more pings at longer intervals (so that if it doesn't get a response the single check retries at 15 second intervals or so before returning a response), but then the check would start taking several seconds or more to complete, and that wouldn't be a good thing. Assuming nagios even allowed a check to run that long - doesn't it have a mechanism to kill a check that doesn't return in a given time frame? I'm a little stumped here how I can adjust things. > What you're asking for is that nagios track that the > child went from down->unreachable->down without an intermediate OK > state and suppress notifications in that case. That would appear to be > a code change and would be better discussed on nagios-devel but I > would encourage the check plugin approach first. Ok. I know there is code in there that know who it sent down messages to and doesn't send up messages to people that didn't get a down (primarily dealing with escalations) so I was hoping that maybe there would be something similar for this, i.e. seeing that the last notification sent was a down notification, and as such there is no need to send another. But if not, so be it. Thanks for the response! ----------------------------------------------- Israel Brewster Computer Support Technician II Frontier Flying Service Inc. 5245 Airport Industrial Rd Fairbanks, AK 99709 (907) 450-7250 x293 ----------------------------------------------- > > -- > Marc <o:p></o:p> </div> </body> </html>