Container Backup Fails: exit code 1

[Proxygen]

[CODE]vzdump xxx --mode snapshot --mailnotification failure --quiet 1 --storage dir_zfs-storage-sdx5 --compress lzo --node node2
102: 2020-04-10 05:30:02 INFO: Starting Backup of VM 102 (lxc)
102: 2020-04-10 05:30:02 INFO: status = running
102: 2020-04-10 05:30:02 INFO: CT Name: example.com
102: 2020-04-10 05:30:02 INFO: backup mode: snapshot
102: 2020-04-10 05:30:02 INFO: bandwidth limit: 128000 KB/s
102: 2020-04-10 05:30:02 INFO: ionice priority: 8
102: 2020-04-10 05:30:02 INFO: create storage snapshot 'vzdump'
102: lxc-freeze: 102: freezer.c: do_freeze_thaw: 54 Failed to freeze 102
102: lxc-freeze: 102: tools/lxc_freeze.c: main: 89 Failed to freeze /var/lib/lxc:102
102: snapshot create failed: starting cleanup
102: no lock found trying to remove 'backup'  lock 
102: 2020-04-10 05:30:02 ERROR: Backup of VM 102 failed - command '/usr/bin/lxc-freeze -n 102' failed: exit code 1

[/CODE]

There is plenty of space in the disk, and the same vzdump run worked fine for all the virtual machines.

 

[fabian]

anything special inside that container? FUSE mountpoints? network shares mounted within the container? could you include the config and pveversion -v as well?

 

[Proxygen]

anything special inside that container? FUSE mountpoints? network shares mounted within the container? could you include the config and pveversion -v as well?

the backup for all containers failed (15+). never had this problem before. none have any secondary mountpoints, internal or external, of any FS type. They are all single disk. do you still want to see the CT conf?

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-19
libpve-guest-common-perl: 3.0-6
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.0-2
lxcfs: 4.0.2-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-5
pve-container: 3.1-1
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.0-5
pve-qemu-kvm: 4.2.0-1
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-13
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

 

[fabian]

no, I can reproduce it, thanks!

 

[fabian]

restarting the containers should allow you to continue with backups and regular operations. if this is a production system I would advise to not run with the pvetest repository enabled permanently!

 

[Proxygen]

i'm not sure why pvetest was enabled. I've disabled the repo. is there any package I need to remove/reinstall?

 

[fabian]

i'm not sure why pvetest was enabled. I've disabled the repo. is there any package I need to remove/reinstall?

no, you can just wait for your regular repository (no-subscription or enterprise) to catch up.

 

[Didier Misson]

Hello. Same error today on my 2 Proxmox !
Never see before

NFO: total size is 4,231,215,888 speedup is 1.05
INFO: first sync finished (24 seconds)
INFO: suspend vm
INFO: lxc-freeze: 325: freezer.c: do_freeze_thaw: 54 Failed to freeze 325
INFO: lxc-freeze: 325: tools/lxc_freeze.c: main: 89 Failed to freeze /var/lib/lxc:325
ERROR: Backup of VM 325 failed - command 'lxc-freeze -n 325' failed: exit code 1
INFO: Failed at 2020-05-13 09:38:10
INFO: Backup job finished with errors
TASK ERROR: job errors

Yesterday, apply upgrade on the 2 Proxmox...
Perhaps link to this upgrade ?
I not yet reboot the Proxmox servers...

 

[Didier Misson]

My backup problem (Failed to freeze) seem link to the 6.2.4 upgrade yesterday.
STOP / START the container, and backups are ok !

 

[coNemniatEND]

I had similar issue, once I rebooted proxmox server it was able to backup with no issues