vzctl --skiplock set 118 --swappages 0 --diskspace 20G:22G


Dec 6, 2018
Cape Town, South Africa

Yes I know this is very old but there is a reason for this, I have a container that I want to upgrade but I'm getting this error:

command 'vzctl --skiplock set 118 --swappages 0 --diskspace 20G:22G --diskinodes 4000000:4400000 --save' failed: exit code 139 (500)

I'm running this through the proxmox gui.

What can I do to fix this?

vzctl, really?

we skipped openvz since many years ...
not really, I moved my OpenVZ all my container years ago to LCX.

I suggest you ask on then openvz mailing lists.
Okay, so this was the only node left on the cluster, and the other node still showed. It popped up randomly "cluster not ready - no quorum? ".

Ran command: "pvecm expected 1" and ran the command above again and worked perfect.



The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!