Every night "systemd Killing process <pid> (systemctl) with signal SIGKILL."

Troubleshooting
1

Hello,
I’ve updated our checkmk dev environment from 1.6.0p21 to 2.0.0p9 and since then I get the following systemd message every night at around 0:00 on rhel8 systems, where a checkmk site is running:

Sep 20 00:00:04 host123 systemd[1]: user@991.service: Killing process 526424 (systemctl) with signal SIGKILL.
Sep 20 00:00:04 host123 systemd[1]: user@991.service: Succeeded.
Sep 20 00:00:04 host123 systemd[1]: Stopped User Manager for UID 991.
Sep 20 00:00:04 host123 systemd[1]: Stopping /run/user/991 mount wrapper...
Sep 20 00:00:04 host123 systemd[1]: Removed slice User Slice of UID 991.
Sep 20 00:00:04 host123 systemd[861361]: run-user-991.mount: Succeeded.
Sep 20 00:00:04 host123 systemd[1578]: run-user-991.mount: Succeeded.
Sep 20 00:00:04 host123 systemd[1]: user-runtime-dir@991.service: Succeeded.
Sep 20 00:00:04 host123 systemd[1]: Stopped /run/user/991 mount wrapper.

This then leads to escalation due to the systemd service being monitored.
“991.service” is the id of the site user.

Any ideas what happend there every night, is this normal behaviour?

regards
Christian

2

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.