Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: b98e4a3c5d263473c5273d8d4f4c3a22b8eb46bf https://github.com/tribe29/checkmk/commit/b98e4a3c5d263473c5273d8d4f4c3a22b… Author: Moritz Kiemer &lt;moritz.kiemer(a)tribe29.com&gt; Date: 2020-01-27 (Mon, 27 Jan 2020) Changed paths: A .werks/10592 M checks/ipmi Log Message: ----------- 10592 FIX ipmi: Go to CRIT if a sensor reports "In critical array" Change-Id: I8f0e2a9832bf297d7b57e4f496a0388b2d40f168 Commit: d342d63a8d89c42d4c8b003403b6681d152952cf https://github.com/tribe29/checkmk/commit/d342d63a8d89c42d4c8b003403b6681d1… Author: Lars Michelsen &lt;lm(a)tribe29.com&gt; Date: 2020-01-27 (Mon, 27 Jan 2020) Changed paths: A .werks/10710 M agents/cfg_examples/systemd/check_mk@.service Log Message: ----------- 10710 FIX systemd: Do not mark the agent unit failed on single agent failure When the agent is queried via systemd, the socket unit creates an instance of the agent service unit template. These are named something like <tt>check-mk-agent@842-127.0.0.1:6556-127.0.0.1:33196.service</tt>. When one of these services failed in the past for some reason, the unit was left in a failed state and reported by the Checkmk systemd service monitoring as a failed service. In reality such errors can occur sporadically for various reasons. However, they are usually uninteresting. For this reason, the agent is now executed in such a way that erroneous executions do not lead to a faulty unit. Change-Id: I670c6e97b165b5209edb79688da485d4412dedaa Compare: https://github.com/tribe29/checkmk/compare/90daf012fc32...d342d63a8d89