Stuff like this always happens/breaks after a vzctl update, whether it's new parameters being added or required etc..

File /etc/vz/conf/ve-vps.basic.conf-sample not found: No such file or directory
Fix the value of CONFIGFILE in /etc/vz/vz.conf
Creation of container private area failed
Warning: distribution not specified in CT config, using defaults from /etc/vz/dists/default
WARNING: /etc/vz/conf/4400.conf not found: No such file or directory


Note the CONFIGFILE is set as "vps.basic" in /etc/vz/vz.conf

CONFIGFILE="vps.basic"

The config file used in this case is /etc/vz/conf/ve-vps.basic.conf-sample


ls /etc/vz/conf/
ve-basic.conf-sample

So either change the filename to ve-vps.basic.conf-sample OR change the CONFIGFILE=basic

I changed it to CONFIGFILE=basic

Basically what happened is the vzctl update must have decided to break previous compatibility and create a new config file "ve-basic.conf-sample" and delete the original

etc, vz, conf, ve, vps, directory, openvz, solutionstuff, vzctl, update, parameters, configfile, creation, container, specified, ct, config, defaults, dists, default, quot, ls, filename, previous, compatibility, delete,

Latest Articles