Werk #9601: Fix failed user services after SSH login
| Component | Firmware |
| Title | Fix failed user services after SSH login |
| Date | Aug 2, 2024 |
| Level | Trivial Change |
| Class | Bug Fix |
| Compatibility | Compatible - no manual interaction needed |
| Appliance Version | 1.7.6 |
Beginning with firmware 1.7.0 logging into a site via SSH resulted in a failed service for the systemd user manager. This Werk fixes the issue.
The error was visible, when the appliance was monitored with checkmk.
After a user logged into the site through SSH, the service Systemd Service
Summary changed the state to CRIT and showed a summary like
1 static service failed (user@999).
Please note that the user ID in these examples is 999,
other IDs are possible as well if an appliance hosts multiple sites.
Details:
Before this change cgrulesengd has been used to assign processes started by members of the omd group to a cgroup whose usable memory was limited. The switch to Debian 12 did not make this work as expected anymore.
The previously used cgrulesengd has been replaced by using systemd slices instead. Along with this services have been converted to systemd units in order to benefit from the resource control capabilities of systemd.
The OOM killer will start killing processes (of checkmk sites) if the memory limit is reached. In combination with #9601 this can lead to sites being killed unexpectedly. In case of a virtual appliance please make sure you assign sufficient memory (at least 4GB) to the virtual machine.