OpenVZ Forum

Today's Messages (off)  | Unanswered Messages (on)

Forum: Support
 Topic: Update killed cgroups and vcmmd
icon8.gif  Update killed cgroups and vcmmd [message #53752] Fri, 23 July 2021 05:55
azilber is currently offline  azilber
Messages: 15
Registered: May 2015
Location: Malaysia
Junior Member
From: 202.185.197*
I've been running yum update for a while and everything was for a few months. Today I decided to do a last yum update and rebooted.
vcmmd refuses to startup with:
2021-07-23 05:28:02 CRITICAL vcmmd: IOError: [Errno 2] No such file or directory: '/sys/fs/cgroup/memory/user.slice/memory.cache.limit_in_bytes'

Doing systemd-cgls showed user.slice wasn't running.

Funny enough, if I run systemctl start user.slice, followed by screen, and then run vcmmd -i from screen, it runs. So for some reason, systemd is not longer creating the correct user.slice cgroups for vcmmd.

Any ideas? This seems like a systemd issue.

So to re-iterate, the workaround right now to get this thing working janky is:
1. systemctl start user.slice
2. screen
3. vcmmd -i

I've dug around some more, and it looks like I can start vcmmd with systemctl, after I manually do systemctl start user.slice. But doing a status on user.slice shows wrong info, and it doesn't startup properly on boot.
So the issue I think is there some form of corruption or bug relating to cgroups and user.slice in systemd.

For example, after reboot:
# systemctl status user.slice
‚óŹ user.slice - User and Session Slice
   Loaded: loaded (/usr/lib/systemd/system/user.slice; static; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd.special(7)

So, this looks like it may be a bug actually in vcmmd. vcmmd is expecting to read user.slice data, but it's operating out of system.slice, and user.slice doesn't seem to automatically get created on boot... ??

# cat /etc/redhat-release
Virtuozzo Linux release 7.9

[Updated on: Fri, 23 July 2021 15:08]

Report message to a moderator

Current Time: Thu Jul 29 09:38:49 GMT 2021