Potential bug with Nag 2.5 scheduled downtime.

[Stanley Hopcroft]

Dear Folks,

I am writing to note a potential bug in Nagios 2.5 (RHEL 3, built from
a SPEC hacked from Dag Wieers).

The bug is that downtime persists after the web interface shows it
should have expired.

For example here is what the extended information panel says about the
host NBASW201

[sh1517 at acisf011 switches]$ lynx -nolist -dump -auth=foo:bar
'http://localhost/nagios/cgi-bin/extinfo.cgi?type=1&host=NBASW201'

  ...

  Host
  NBASW201
  Member of
  Bar-switches
  a.b.c.d

  Host State Information
  Host Status:
    UP
  Status Information:            PING OK - Packet loss = 0%, RTA = 3.68 ms
  Performance Data:
  Current Attempt:               0/10
  State Type:                    HARD
  Last Check Type:               ACTIVE
  Last Check Time:               03-08-2006 21:28:15
  Status Data Age:               0d 13h 40m 1s
  Next Scheduled Active Check:   N/A
  Latency:                       0.000 seconds
  Check Duration:                0.013 seconds
  Last State Change:             03-08-2006 21:28:15
  Current State Duration:        0d 13h 40m 1s
  Last Host Notification:        N/A
  Current Notification Number:   0
  Is This Host Flapping?         N/A
  Percent State Change:          N/A
  In Scheduled Downtime?
    YES
  Last Update:                   04-08-2006 11:08:10
  Active Checks:
    ENABLED
  Passive Checks:
    ENABLED
  Obsessing:
    ENABLED
  Notifications:
    ENABLED
  Event Handler:
    ENABLED
  Flap Detection:
    ENABLED


But here is what the downtime.dat file reports (and for another host
that was also subject to scheduled downtime and remains in it).

hostdowntime {
       host_name=NBASW201
       downtime_id=2
       entry_time=1154600113
       start_time=1154600014
       end_time=1154610000
       triggered_by=1
       fixed=0
       duration=10800
       author=Peter Zafiris
       comment=Building Switch Move
       }

hostdowntime {
       host_name=NBASW202
       downtime_id=3
       entry_time=1154600113
       start_time=1154600014
       end_time=1154610000
       triggered_by=1
       fixed=0
       duration=10800
       author=Peter Zafiris
       comment=Building Switch Move
       }

The times are

[root at acisf011 nagios]# perl -ne 'next unless /(\w+_time)=(\d+)/;
print $1, "\t", localtime($2) . "\n"' downtime.dat
entry_time      Thu Aug  3 20:15:13 2006
start_time      Thu Aug  3 20:13:34 2006
end_time        Thu Aug  3 23:00:00 2006
entry_time      Thu Aug  3 20:15:13 2006
start_time      Thu Aug  3 20:13:34 2006
end_time        Thu Aug  3 23:00:00 2006
entry_time      Thu Aug  3 20:15:13 2006
start_time      Thu Aug  3 20:13:34 2006
end_time        Thu Aug  3 23:00:00 2006
entry_time      Thu Aug  3 20:15:13 2006
start_time      Thu Aug  3 20:13:34 2006
end_time        Thu Aug  3 23:00:00 2006
entry_time      Thu Aug  3 20:15:13 2006
start_time      Thu Aug  3 20:13:34 2006
end_time        Thu Aug  3 23:00:00 2006
[root at acisf011 nagios]#

[root at acisf011 nagios]# date
Fri Aug  4 11:05:04 EST 2006
[root at acisf011 nagios]#

So all the end_times should have expired but the web interface in all
the status screens is still reporting the hosts in scheduled downtime

Yours sincerely,

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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