[checkmk-commits] [tribe29/checkmk] c6659e: 12758 FIX notification replay not working and erro...

Branch: refs/heads/2.0.0 Home: https://github.com/tribe29/checkmk Commit: c6659e505913b80523892d428739c50413f8ff90 https://github.com/tribe29/checkmk/commit/c6659e505913b80523892d428739c5041… 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 Commit: 4e043c92f71b8787ef0f956059292b7a19827baf https://github.com/tribe29/checkmk/commit/4e043c92f71b8787ef0f956059292b7a1… Author: Mathias Laurin <mathias.laurin(a)tribe29.com> Date: 2021-04-29 (Thu, 29 Apr 2021) Changed paths: M cmk/fetchers/snmp.py Log Message: ----------- Save SNMP discovery cache into directory This should avoid a possible name conflict with a host whose name ends in .discovery CMK-7752 Change-Id: Ib9989774eed7d64c99ceb0be9708c2888cd36331 Compare: https://github.com/tribe29/checkmk/compare/6ef4ab22dd2a...4e043c92f71b