Sad to say systemd failed check_mk is back again :-(

with agent 1.6.0p11 CEE there is still a critical error if check_mk agent fails. It’s not
fixed by systemd: Do not mark the agent unit failed on single agent failure as it seems. Any Suggestions,
it’s really annoying…

Apr 21 10:04:09 systemd[1]: Got more than one socket.
Apr 21 10:04:09 systemd[1]: check_mk@6265-xx.xx.xx.xx:6556-yy.yy.yy.yy:23706.service failed to run ‘start’ task: Invalid argument
Apr 21 10:04:09 systemd[1]: Failed to start Check_MK.
– Subject: Unit check_mk@6265-xx.xx.xx.xx:6556-yy.yy.yy.yy:23706.service has failed

I use the systemd service rule now with the exclude regex pattern option:
check_mk@.*

Works for me - but sad to know that fixed bugs are coming up again. Should be
handled by the client isn’t it?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.