Module: check_mk Branch: master Commit: aea18ed983fa91d6e8ee13cf374f9fb20f5c052f URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=aea18ed983fa91… Author: Sven Panne <sp(a)mathias-kettner.de> Date: Wed Apr 4 13:11:33 2018 +0200 5830 FIX Fixed DST shift correction for downtimes, causing CMC to use 100% CPU When a downtime was configured to recur every hour and a 1h DST shift happened, the CMC would go into an infinite loop with 100% CPU load and no monitoring at all. If the downtime in question was set in an ad hoc fashion via the GUI (not via rules), the only way to work around this issue was to remove the state file, losing all downtimes, acknowledgements and comments. Change-Id: Iebca5c808b39947682da235b08dffb73a883299b --- .werks/5830 | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/.werks/5830 b/.werks/5830 new file mode 100644 index 0000000..04e9074 --- /dev/null +++ b/.werks/5830 @@ -0,0 +1,14 @@ +Title: Fixed DST shift correction for downtimes, causing CMC to use 100% CPU +Level: 2 +Component: core +Compatible: compat +Edition: cee +Version: 1.5.0i4 +Date: 1522839759 +Class: fix + +When a downtime was configured to recur every hour and a 1h DST shift +happened, the CMC would go into an infinite loop with 100% CPU load and no +monitoring at all. If the downtime in question was set in an ad hoc fashion +via the GUI (not via rules), the only way to work around this issue was to +remove the state file, losing all downtimes, acknowledgements and comments.