[SOLVED] Entire server is locked - VM is locked (backup) (500) error code

[petermatra]

Hi, all of my machines run and backups are running fine but I cannot add VMs. I constantly get this error. I tried 'qm unlock VMID' on every machine I have and I also tried physically removing the lock files from the /var/local/qemu-server directory and that didn't help. What is causing this and how do I stop it?

 

[fiona]

Hi,
that does strange indeed. Please post the output of pveversion -v and check your backup logs for any errors/warnings. When you try to add a VM, did you use an ID that was already used in the past? Or does it also happen when using an ID that you never used in the past? Please post the full output of such a create command, example: qm create 123456789.

 

[petermatra]

I am using IDs that were used in the past.

qm create 123456789

worked and created a VM. I had just deleted several VMs and planned on replacing them via terraform until I got this message.

Output from pveversion -v

proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-5.15: 7.3-1
pve-kernel-helper: 7.3-1
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u2
proxmox-backup-client: 2.3.2-1
proxmox-backup-file-restore: 2.3.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-2
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.7-pve2

I'm going to update my server, since there are several updates waiting.

qm create 116 works and creates a vm, but when I try to create a VM via terraform or clone a template I get the error message. I tried to create a clone on 150, or even 500 I get the error.

I think I've attached the correct backup log

I tried cloning manually and that didn't work

root@pve:~/Terraform-K8-multinic-promox# pvesh create nodes/pve/qemu/9003/clone --newid 116 --full --name=k3-server
VM is locked (backup)
root@pve:~/Terraform-K8-multinic-promox# pvesh create nodes/pve/qemu/9003/clone --newid 500 --full --name=k3-server
VM is locked (backup)
root@pve:~/Terraform-K8-multinic-promox# pvesh create nodes/pve/qemu/9003/clone --newid 700 --full --name=k3-server
VM is locked (backup)

Here is another update: I'm able to create a machine from and OS file. But not a template or terraform.

 

[petermatra]

I got it to work. I had to unlock the templates I'm cloning from. Thanks for your help.

 

[fiona]

I got it to work. I had to unlock the templates I'm cloning from. Thanks for your help.

Glad you were able to solve the issue! You can mark the thread as [SOLVED] by selecting Edit thread and selecting the appropriate prefix. This helps other users to find solutions more quickly.

Was the backup for the template running at that moment? Or was there an error that kept the template locked (you can check the backup log).

 

[petermatra]

I couldn't find the error in the logs. But my guess was a failed backup from a power outage. The template was not running at the time.