Mknotifyd cant start after upgrade to 2.1.0p17

After upgrading to 2.1.0p17 all of our slavesites mknotifyd cant start.
Logs says the following, so I turned off the encryption and it started ok.
But I dont want to this to be unencrypted so is this a known bug and is there a fix in the works?

2022-12-13 10:02:42,570 [20] [cmk.mknotifyd] -----------------------------------------------------------------
2022-12-13 10:02:42,570 [20] [cmk.mknotifyd] Check_MK Notification Spooler version 2.1.0p17 starting
2022-12-13 10:02:42,571 [20] [cmk.mknotifyd] Log verbosity: 0
2022-12-13 10:02:42,584 [20] [cmk.mknotifyd] Daemonized with PID 2545001.
2022-12-13 10:02:42,594 [40] [cmk.mknotifyd] FATAL ERROR:
Traceback (most recent call last):
File “/omd/sites/halcyon/lib/python3/cmk/cee/mknotifyd/main.py”, line 307, in main
run_notifyd(args, config, paths, start_time)
File “/omd/sites/halcyon/lib/python3/cmk/cee/mknotifyd/main.py”, line 62, in run_notifyd
connection_manager.initialize_stunnel()
File “/omd/sites/halcyon/lib/python3/cmk/cee/mknotifyd/connection_manager.py”, line 192, in initialize_stunnel
config: str = create_stunnel_config_from_mknotifyd_config(
File “/omd/sites/halcyon/lib/python3/cmk/cee/mknotifyd/connection_manager.py”, line 46, in create_stunnel_config_from_mknotifyd_config
if incoming and incoming[“encryption”] != “unencrypted”:
KeyError: ‘encryption’

Have you seen this Werk? I think you are hitting this very problem.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.