[checkmk-commits] [tribe29/checkmk] 76bc3a: Minor reformatting in checks/cmciii

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 76bc3a48164a714752d403c8adb4b0bdcfc058d3 https://github.com/tribe29/checkmk/commit/76bc3a48164a714752d403c8adb4b0bdc… Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com> Date: 2021-04-29 (Thu, 29 Apr 2021) Changed paths: M checks/cmciii Log Message: ----------- Minor reformatting in checks/cmciii Change-Id: Icdca8a608370323851bdf5bfbbb716fc67cbe546 Commit: 2bc8dd4b96a12b80712be10164002ca63b573e6b https://github.com/tribe29/checkmk/commit/2bc8dd4b96a12b80712be10164002ca63… Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com> Date: 2021-04-29 (Thu, 29 Apr 2021) Changed paths: A .werks/12758 M cmk/base/autochecks.py Log Message: ----------- 12758 FIX notification replay not working and errors in the cmc.log If a "Recent notification (for analysis)" in Setup -> Events -> Notifications was replayed an error message was shown in the User interface. Furthermore, the error message: invalid signal byte ASCII 76, expected '*' read 76 further bytes: 'oading autochecks from /omd/sites/stable/var/check_mk/autochecks/stable.mk was logged in the cmc.log if a notification was sent. This is fixed. The reason was that when the labels of a service in complete_raw_context were loaded a message was printed to the console in autochecks.py. This interfered with the notification communication of the CMC. The console logging is now replaced with the logger module. Messages are now logged in the notify.log. When the command line (e.g. cmk -vII HOST) is used messages are printed to stdout as before. CMK-6123 Change-Id: Ibd06516ea71f6e3005ce76d4fc59937364b29234 Compare: https://github.com/tribe29/checkmk/compare/6b70a4f08865...2bc8dd4b96a1