As the subject states, we just noticed a new kernel was released and updated/rebooted a few of our non-production hosts. They all have the same issue when attempting to start a container. You can't start a container and get this error:
Failed to start the CT: PRL_ERR_VZCTL_OPERATION_FAILED (Details: vcmmd: failed to register Container: Failed to get VCMMD D-Bus name
vcmmd: failed to unregister Container: Failed to get VCMMD D-Bus name
vcmmd: failed to unregister Container: Failed to get VCMMD D-Bus name
Failed to start the Container
)
I noticed that vcmmd.service is stuck "activating", and looking at the vcmmd.log it's failing with this:
2024-01-25 09:30:26 INFO vcmmd: Started
2024-01-25 09:30:26 INFO vcmmd.config: Loading config from file '/etc/vz/vcmmd.conf'
2024-01-25 09:30:26 INFO vcmmd.host: ovz7-10.brownrice.com: 134722818048 bytes available for VEs
2024-01-25 09:30:26 ERROR vcmmd.host: ovz7-10.brownrice.com: Memory cgroup vstorage.slice does not exist
2024-01-25 09:30:26 ERROR vcmmd.ldmgr: Failed to load policy "density": Policy not found
2024-01-25 09:30:26 INFO vcmmd.ldmgr: Switch to fallback policy
2024-01-25 09:30:26 INFO vcmmd.ldmgr: Loaded policy "NoOpPolicy"
2024-01-25 09:30:26 CRITICAL vcmmd: Terminating program due to unhandled exception:
2024-01-25 09:30:26 CRITICAL vcmmd: Traceback (most recent call last):
2024-01-25 09:30:26 CRITICAL vcmmd: File "/usr/lib/python3.6/site-packages/vcmmd/util/threading.py", line 43, in run_with_except_hook
2024-01-25 09:30:26 CRITICAL vcmmd: run_original(*args2, **kwargs2)
2024-01-25 09:30:26 CRITICAL vcmmd: File "/usr/lib64/python3.6/threading.py", line 864, in run
2024-01-25 09:30:26 CRITICAL vcmmd: self._target(*self._args, **self._kwargs)
2024-01-25 09:30:26 CRITICAL vcmmd: File "/usr/lib/python3.6/site-packages/vcmmd/ldmgr/policy.py", line 82, in wrapper
2024-01-25 09:30:26 CRITICAL vcmmd: sleep_timeout = f(self, *args, **kwargs)
2024-01-25 09:30:26 CRITICAL vcmmd: File "/usr/lib/python3.6/site-packages/vcmmd/ldmgr/policy.py", line 323, in ksm_controller
2024-01-25 09:30:26 CRITICAL vcmmd: params = self.get_ksm_params()
2024-01-25 09:30:26 CRITICAL vcmmd: File "/usr/lib/python3.6/site-packages/vcmmd/ldmgr/policies/NoOpPolicy.py", line 54, in get_ksm_params
2024-01-25 09:30:26 CRITICAL vcmmd: if self.active_vm < ksm_vms_active_threshold or \
2024-01-25 09:30:26 CRITICAL vcmmd: AttributeError: 'NoOpPolicy' object has no attribute 'active_vm'
Is anyone else running into this? I have the same issue on all 4 hosts that I updated yesterday.
Thanks!,
OpenVZ Forum
Members
Search
Help
Register
Login
Home
