Guest killed if backup stopped

[Valerio Pachera]

I was running a backup (snapshot).
I chose to stop the backup because I wanted to exclude a disk.
After stopping it, the guest wasn't running anymore:

INFO: starting new backup job: vzdump 100 --mode snapshot --compress lzo --storage usb-esterno --remove 0 --node pve
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: update VM 100: -lock backup
INFO: VM Name: dc
INFO: include disk 'ide0' 'local-zfs:vm-100-disk-1' 200G
INFO: include disk 'virtio1' 'meccanico:vm-100-disk-1' 600G
INFO: exclude disk 'virtio2' 'meccanico:vm-100-disk-2' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/media/esterno/dump/vzdump-qemu-100-2017_09_07-21_18_52.vma.lzo'
INFO: started backup task '7f6ae1a0-c9a5-44f5-ab3a-cc8b2f08c49d'
INFO: status: 0% (496107520/858993459200), sparse 0% (2146304), duration 3, read/write 165/164 MB/s
INFO: status: 1% (8657764352/858993459200), sparse 0% (44806144), duration 73, read/write 116/115 MB/s
INFO: status: 2% (17204314112/858993459200), sparse 0% (44859392), duration 167, read/write 90/90 MB/s
INFO: status: 3% (25794183168/858993459200), sparse 0% (199393280), duration 331, read/write 52/51 MB/s
ERROR: interrupted by signal
INFO: aborting backup job
ERROR: VM 100 qmp command 'backup-cancel' failed - client closed connection
ERROR: Backup of VM 100 failed - interrupted by signal
ERROR: Backup job failed - interrupted by signal
TASK ERROR: interrupted by signal

Proxmox 5.0-30.

 

[dcsapak]

mhmm works here,
whats the output of

pveversion -v

?

 

[Valerio Pachera]

pveversion -v
proxmox-ve: 5.0-20 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-4
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4                                                                                                                                                                               
smartmontools: 6.5+svn4324-1                                                                                                                                                                   
zfsutils-linux: 0.6.5.11-pve17~bpo90

 

[mbaldini]

Have you tried

qm unlock 100

?

 

[Valerio Pachera]

@mbaldini there's no need to unlock the guest.
The problem is that the guest got killed by proxmox when I stopped running the backup.

 

[RolandK]

i have a similar problem with recent proxmox

when i use "stop" in the backup task, then i get

INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '2ba4acfa-1d0d-49ef-8a19-f77db420eff4'
INFO: resuming VM again
INFO: 0% (54.4 MiB of 260.0 GiB) in 3s, read: 18.1 MiB/s, write: 17.8 MiB/s
INFO: 1% (2.6 GiB of 260.0 GiB) in 3m 13s, read: 13.8 MiB/s, write: 13.8 MiB/s
ERROR: interrupted by signal
INFO: aborting backup job

after that, in the task view i see "Error: unexpected status"

after that, i can still ping the affected VM, but i cannot login anymore. i get to an ssh loginprompt, but after login it times out, i guess I/O inside the vm is frozen

the guest is locked and i can get no console.

after "qm unlock" this is no better, i need to stop/reboot the VM

 

[RolandK]

for my own reference :
https://bugzilla.proxmox.com/show_bug.cgi?id=2723
https://bugzilla.proxmox.com/show_bug.cgi?id=3225

maybe it's a different issue, as you write VM is getting killed.