[Users] vcmmd broken after last update, CT/VM cannot start

[Dmitry Konstantinov]

Don't have this problem using both prlctl and vzctl. Centos-7 based 
container. Please note that it was on a fresh openvz installation.


===

# prlctl stop e410c4d0-91e2-4aef-afe4-14204f19316e
WARNING: You are using a deprecated CLI component that won't be 
installed by default in the next major release. Please use virsh instead
Stopping the CT...
The CT has been successfully stopped.
# prlctl start e410c4d0-91e2-4aef-afe4-14204f19316e
WARNING: You are using a deprecated CLI component that won't be 
installed by default in the next major release. Please use virsh instead
Starting the CT...
The CT has been successfully started.
# vzctl status e410c4d0-91e2-4aef-afe4-14204f19316e
VEID e410c4d0-91e2-4aef-afe4-14204f19316e exist mounted running
# cat /etc/virtuozzo-release
OpenVZ release 7.0.20 (147)
[root at ssd33-ga ~]# rpm -qi vcmmd
Name        : vcmmd
Version     : 8.0.77
Release     : 1.vz7
Architecture: noarch
Install Date: Thu 21 Dec 2023 01:27:53 PM CST
Group       : System Environment/Base
Size        : 466446
License     : GPLv2 with exceptions
Signature   : RSA/SHA256, Fri 28 Apr 2023 12:34:29 PM CDT, Key ID 
ca0b7d1944cdad2a
Source RPM  : vcmmd-8.0.77-1.vz7.src.rpm
Build Date  : Fri 28 Apr 2023 12:33:44 PM CDT
Build Host  : builder9.eng.sw.ru
Relocations : (not relocatable)
Packager    : Virtuozzo (http://www.virtuozzo.com/support/)
Vendor      : Virtuozzo
Summary     : Virtuozzo memory management daemon
Description :
vcmmd is a daemon that watches Virtuozzo containers and tunes their memory
configuration parameters according to the current memory demand.
#

On 1/30/24 04:26, Aurélien GUERSON wrote:
> The problem seems to be inside the python dir here :
> 
> /usr/lib/python3.6/site-packages/
> 
> 
> For the moment, to bypass
> 
> yum update --exclude=vcmmd,libvcmmd --skip-broken
> 
> 
> Waiting for a update
> 
>