Hi Ronny,
the only thing I’ve found was an entry at /var/log/messages:
Nov 23 16:34:35 systemd: Starting Check_MK (<ip-address of check-mk-server>:33118)...
Nov 23 16:36:50 systemd: check_mk@914-10.2.16.144:6556-<ip-address of check-mk-server>:33118.service start operation timed out. Terminating.
Nov 23 16:36:50 systemd: Failed to start Check_MK (<ip-address of check-mk-server>:33118).
Nov 23 16:36:50 systemd: Unit check_mk@914-10.2.16.144:6556-<ip-address of check-mk-server>:33118.service entered failed state.
Nov 23 16:36:50 systemd: check_mk@914-10.2.16.144:6556-<ip-address of check-mk-server>:33118.service failed.
Nov 23 16:36:50 systemd: Starting Check_MK (<ip-address of check-mk-server>:43208)...
Nov 23 16:36:55 systemd: Started Check_MK (<ip-address of check-mk-server>:43208).
Check-mk is running normally, but the systemd check goes critical after that. Any suggestions
for configuring the agent under /etc/xinet.d/check_mk ?
Could it be the case to set wait = yes in /etc/xinet.d/check_mk. It’s a single call per check intervall
right?
Regards
Guenther