<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> <TITLE>Message</TITLE> <META content="MSHTML 6.00.2800.1476" name=GENERATOR><o:SmartTagType name="PersonName" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType> <STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } SPAN.EmailStyle18 { COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>1 - Are you going by the timestamps in the actual email or at what time you received the email? I know often times we get an alert that seems strange and then check the actual time IN the email and it turns out to be just a delayed email that finally got sent. ( Especially when the email server you are using to send the nagios emails goes down and it sends a CRITICAL about the mail server. Usually we end up getting the OK message before we get the CRITICAL message, but the timestamps within the email are correct. )</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>2 - No, it won't be preceeded by service failures. If a service fails, I believe it checks the host. If the host works, then it sends a service notification. Otherwise, if the host doesn't work, it just sends a host alert and doesn't bother with all the service checks. After all, if the host is down, you know all the services are going to be.</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>3 - Can you paste the stanza for your check_http service check? What's your retry_check_interval? max_check_attempts? These all play into when a notification is sent, because a notification is only sent upon change of state and those parameters all concern when nagios declares a change of state. Recently, we know we had a problem with SMTP, so we only wanted to be notified if the problem continued for 30 minutes, so our stanza ended up looking like this.</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>define service {<BR> use generic-service<BR> hostgroup_name webfarm</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2> service_description SMTP<BR> max_check_attempts 6<BR> retry_check_interval 5<BR> check_command check_smtp<BR>}</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>It basically means that when the service fails for the first time, nagios will try again 5 more times, at 5 minute intervals, before it declares SMTP as critical and notifies us. I really can't say what's wrong with your config without seeing the stanzas, but I hope this helps.</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>--</FONT></SPAN></DIV> <DIV><SPAN class=144280819-16112004><FONT face=Arial color=#0000ff size=2>sh</FONT></SPAN></DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Jon Gefaell [mailto:jgefaell@netblue.com] <BR><B>Sent:</B> Tuesday, November 16, 2004 10:46 AM<BR><B>To:</B> nagios-users@lists.sourceforge.net<BR><B>Subject:</B> [Nagios-users] Various timing related issues with Nagios, critical impact on monitoring.<BR><BR></FONT></DIV> <DIV class=Section1> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy">Not only am I having problems with the notification interval, other strangeness is rearing it's head. Last night there was a host down alarm, no service check problems, just a host down. Then, 40 seconds (SECONDS!) later, Host OK. What could possibly explain this? There's no check interval of 40 seconds... And shouldn't a host check be preceeded by service failures?<o:p></o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy">Another host had an check_http service check timeout. Generated a critical alert notificiation. Nothing else until 20 minutes later when it went 'OK. This is confusing, Given that my notification interval seems stuck at 25 minutes it makes sense we only got one notification, but our alternate alarm systems (remote services) never alarmed at all, the service was fully available during these 20 minutes. The alarm was just a timeout on the plugin and then it seems nothing happened for 20 minutes???<o:p></o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy">I set notification interval to 15 and still get notifications every 25 minutes. I can't figure it out.<o:p></o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy"><o:p> </o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy">Please do try to help address these issues, our use of Nagios is heavily impacted by the inability to configure things like the notification interval and the other behaviours described here.<o:p></o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy"><o:p> </o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy">---<o:p></o:p></SPAN></FONT></P> <P><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">Hello,<BR><BR>I am running Nagios 1.2 on Linux Redhat 9 and 7.3<BR><BR>I am seeing that if a service condition is let's say 'warning' and remains that way notifications are sent every 25 minutes.<BR><BR>Now I have interval_length=60 and notification_interval 120<BR><BR>This makes me think that I should be getting these notifications every 2 hours, which is the desired behaviour. Can anyone tell me what may be wrong here? Maybe I don't understand this properly? Are these two parameters what should be controlling this behaviour?<BR><BR>Thank you very much for your kind consideration.<BR><BR><st1:PersonName style="BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x" w:st="on">Jon Gefaell</st1:PersonName></SPAN></FONT><o:p></o:p></P></DIV></BLOCKQUOTE></BODY></HTML>