[dev.icinga.com #3822] Downtimes Cronk shows expired downtimes

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3822

Created by aledermueller on 2013-03-11 10:21:45 +00:00

Assignee: (none)
Status: Closed (closed on 2013-10-07 11:07:18 +00:00)
Target Version: (none)
Last Update: 2013-10-07 11:07:18 +00:00 (in Redmine)

Icinga Version: 1.8.4
Icinga Web Version: 1.8.2
IDO Version: 1.8.4
OS Version: Debian Squeeze
DB Type: MySQL
DB Version: 5.5.13
Browser Version: 24.0.1312.56

---

Hi,

The downtime cronk also shows expired downtimes while it should only display active downtimes.

kind regards,
Achim Ledermüller

---

Relations:

• relates #4808
• relates #4809

[icinga-migration]

Updated by mfrosch on 2013-10-02 12:49:04 +00:00

• Target Version set to 1.9.2

[icinga-migration]

Updated by mfrosch on 2013-10-04 09:56:47 +00:00

• Status changed from New to Assigned
• Assigned to set to mfrosch

Problem: under certain unknown circumstances, the core sometime does not delete downtimes.

Therefor they stay in the database forever.

Idea: filter the view to show only downtimes within their active timerange. Only flaw should be that flexible downtimes only disappear after their definitive end timestamp.

[icinga-migration]

Updated by mfrosch on 2013-10-04 10:31:59 +00:00

The downtime only gets removed when an actual downtime_end event occurs.

There is currently no cleanup of downtimes on start of the icinga instance.

[icinga-migration]

Updated by mfrosch on 2013-10-04 10:46:41 +00:00

Will talk to dnsmichi about this on Monday.

[icinga-migration]

Updated by mfrosch on 2013-10-07 11:07:18 +00:00

• Status changed from Assigned to Closed
• Assigned to deleted mfrosch
• Target Version deleted 1.9.2

This is actually not a error in Icinga Web, and I don't want to introduce some timebased filters into the view.

Now 2 Icinga core Bugs are opened:

#4808 - ido2db not clearing downtimes on startup
#4809 - downtimes sometimes not deleted correctly

If someone wants to filter this manually you should use a cronjob that does:

-- use on your own RISK!
DELETE FROM icinga_scheduleddowntimes WHERE scheduled_end_time < NOW();