OpenVZ Solutions vzquota : (error) Can't open quota file for id 123123, maybe you need to reinitialize quota: No such file or directory
Error: Unable to apply new quota values: quota not running
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Killing container ...
Container was stopped
Error: Unable to apply new quota values: quota not running
Can't umount /vz/private/123123: Invalid argument
[root@rtt 123123]# vzquota on 123123
vzquota : (error) Can't open quota file for id 123123, maybe you need to reinit........
OpenVZ - how to manually restore a VPS from another host or backup
There are 3 pieces that are required to restore and make it work (of course consider if any kernel modules need to re-enabled and if you need to change the IPs):
Copy the vz/private/VEID directory to /vz/private
Copy the /etc/vz/conf/VEID.conf to /etc/vz/conf/
mkdir /vz/root/VEID
After that you should be able to see the VE in vzlist -a
You should then be able to start it normally.........
Error: detected vswap CT config but kernel does not support vswap This means either old kernel or bad config (physpages NOT set to 0:unlimited) Solution for OpenVZ
Error: detected vswap CT config but kernel does not support vswap
This means either old kernel or bad config (physpages NOT set to 0:unlimited)
Solution
vzctl set $veid --physpages 0:unlimited --save........
Initializing quota ... Error: Not enough parameters, diskinodes quota not set
Initializing quota ...
Error: Not enough parameters, diskinodes quota not set
vzctl set $veid --diskinodes 90000:91000 --save
New versions of OpenVZ seem to have some strange diskinodes parameter which is required.........
OpenVZ/vzctl how to do an on-line migration without downtime
vzmigrate --online dest-host VEIDNO
eg.:
vzmigrate --oneline 192.168.1.55 101
One option I would recommend is "--keep-dst", that way if the migration is interrupted you can still bring the VPS back up on the original host. After the migration is successful you can manually destroy it.
OpenVZ has a good writeup on this including Checkpointing and Restoring etc:........
Openvz "Container already locked" Error Message Solution/Fix
I didn't find any useful information that actually fixed this. My VPS was in the "Running State" and I could not stop or restart it. I kept getting "Container already locked" no matter what Idid (I tried all the suggestions in the Google results for this error).
Most of the suggestions were for Windows but I only use Linux. The other solutioins also said to restart the VZ service or even the entire hostnode and this was not acceptable to me........