Downtime discrepancy

[Chris Waters]

>From the docs:
 
Fixed vs. Flexible Downtime

When you schedule downtime for a host or service through the web
interface you'll be asked if the downtime is fixed or flexible. Here's
an explanation of how "fixed" and "flexible" downtime differs:

"Fixed" downtime starts and stops at the exact start and end times that
you specify when you schedule it. Okay, that was easy enough...

"Flexible" downtime is intended for times when you know that a host or
service is going to be down for X minutes (or hours), but you don't know
exactly when that'll start. When you schedule flexible downtime, Nagios
will start the scheduled downtime sometime between the start and end
times you specified. The downtime will last for as long as the duration
you specified when you scheduled the downtime. This assumes that the
host or service for which you scheduled flexible downtime either goes
down (or becomes unreachable) or goes into a non-OK state sometime
between the start and end times you specified. The time at which a host
or service transitions to a problem state determines the time at which
Nagios actually starts the downtime. The downtime will then last for the
duration you specified, even if the host or service recovers before the
downtime expires. This is done for a very good reason. As we all know,
you can think you've got a problem fixed (and restart a server) ten
times before it actually works right. Smart, eh?

Flexible means nagios expects the host to go down within the "window"
you have specified for the duration you specified.
 
 

________________________________

From: Andrew Davis [mailto:nccomp at gmail.com] 
Sent: Tuesday, May 19, 2009 9:59 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Downtime discrepancy


Looking at my hosts that are scheduled for downtime, I noticed this:

ns2    05-19-2009 10:55:04    adavis    Rebuilding with CentOS
05-19-2009 10:54:43    05-19-2009 12:54:43    Flexible    0d 3h 0m 0s
49    N/A     Delete/Cancel This Scheduled Downtime Entry

How is it possible to have downtime scheduled from 10:54:43 to 12:54:43
yet have a duration of 3 hours??? Something appears to be amiss.

In fact, even though it was marked as flexible and with a duration of 3
hours, 12:54:43 just passed and the system is no longer listed as being
under downtime, yet it should be as it was scheduled for 3 hours of
downtime.

-- 


  A. Davis
  Email:     nccomp at gmail.com

  "There is no limit to what a man can accomplish
   if he doesn't care who gets the credit." - Ronald Reagan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090519/b2c4715b/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null