<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" 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 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=blue> <div class=Section1> Setting up downtime will not be possible. As our servers our being used by individual users for testing purposes. And they may reboot the machine in the normal process of their working. Asking them to schedule a downtime would add overhead for them and we would not prefer to do that.<o:p></o:p> <o:p> </o:p> So I guess I will have to go with Mark’s suggestion if there is no way to delay the notifications.<o:p></o:p> <o:p> </o:p> Thank you,<o:p></o:p> Lalita<o:p></o:p> <div> <o:p></o:p> From: nagios-users-bounces@lists.sourceforge.net [mailto:nagios-users-bounces@lists.sourceforge.net] On Behalf Of Anthony Montibello Sent: Saturday, July 28, 2007 8:10 AM To: Nagios Users Mailinglist Subject: Re: [Nagios-users] dont want notification when machine reboots<o:p></o:p> </div> <o:p> </o:p> <o:p> </o:p> <div> IF the machines are rebooted at or between a particular time, then setup DOWNTIME, (potentially setting it up in a script) <o:p></o:p> </div> <div> <o:p></o:p> </div> <div> with downtime, there is both fixed and dynamic, <o:p></o:p> </div> <div> using dynamic I find best resembles a reboot senario; you can set it up so that the downtime will begin within a particular time frame, then after the DURATION the downtime ends, because you proboly would like to know if a machine does not go back up within the a specific timelimit. With Fixed it fairly strait foward between here to here ignore notification rules. <o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Mind Host checks are a burden and sometimes induce a load on the Nagios server, thus the sugestion earlier by Mark Powell is always a good way to reduce some of that Host check load.<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Good luck,<o:p></o:p> </div> <div> TOny (author of NC_NEt)<o:p></o:p> </div> <o:p> </o:p> <div> On 7/27/07, Jim Avery <<a href="mailto:jim@jimavery.me.uk">jim@jimavery.me.uk</a>> wrote: <o:p></o:p> I've been having a similar problem and have thought about the solution but haven't gotten around to implementing it yet. Mark Powell's suggestion to rely on the service check notification is absolutely right when you want to ignore brief bounces or lost pings. I'm going to do just that, but I will still have a host notification enabled too... I'll configure things so that the on-call engineers get the ping service notification rather than the host notification - they don't want to know about servers briefly bounced. The host notifications I'll send only to me by email so I will know the next day which servers have bounced overnight. I'm hoping that will bring me the best of both worlds. Cheers, Jim ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using <st1:City w:st="on"><st1:place w:st="on">AJAX</st1:place></st1:City> and a browser. Download your FREE copy of Splunk now >> <a href="http://get.splunk.com/">http://get.splunk.com/</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net </a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> </div> <o:p> </o:p> </div> </body> </html> Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.