qmp command 'query-backup' failed - client closed connection

[informant]

Hi, we have a error on backup, but do not found a solution. following error message comes with backup report mail. vm was not reachable on backup start/on automatical backup. ssh and ping was not reachable. we have hard stop and start the vm 6 hours after. his was not reachable and in this time they wasn´t reachable. after this, it come following message:

5402: Feb 19 01:01:46 INFO: Starting Backup of VM 5402 (qemu)
5402: Feb 19 01:01:46 INFO: status = running
5402: Feb 19 01:01:47 INFO: update VM 5402: -lock backup
5402: Feb 19 01:01:47 INFO: backup mode: snapshot
5402: Feb 19 01:01:47 INFO: ionice priority: 7
5402: Feb 19 01:01:47 INFO: creating archive '/mnt/pve/Storage-1/dump/vzdump-qemu-5402-2015_02_19-01_01_46.vma.gz'
5402: Feb 19 01:01:47 INFO: started backup task 'c5091f4a-bd3b-4696-89e6-ab8677304756'
5402: Feb 19 01:01:50 INFO: status: 0% (0/107374182400), sparse 0% (0), duration 3, 0/0 MB/s
5402: Feb 19 07:04:24 ERROR: VM 5402 qmp command 'query-backup' failed - client closed connection
5402: Feb 19 07:04:24 INFO: aborting backup job
5402: Feb 19 07:04:24 ERROR: VM 5402 not running
5402: [COLOR=red]Feb 19 07:04:24 ERROR: Backup of VM 5402 failed - VM 5402 qmp command 'query-backup' failed - client closed connection[/COLOR]

Any Ideas to fix it or other informations? very thanks

best regards

 

[dietmar]

What is the output of

# pveversion -v

And please can you post the VM config?

 

[informant]

Hi, yes we can:

pveversion -v
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-20 (running version: 3.3-20/d0640ef1)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-30
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

conf:

bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 16384
name: lin03
net0: e1000=52:16:C4:FF:F5:CB,bridge=vmbr0
onboot: 1
ostype: other
sockets: 1
virtio0: local:5402/vm-5402-disk-1.qcow2,format=qcow2,size=100G

do you need more informations?

best regards

 

[dietmar]

What OS do you run inside?

 

[informant]

As VM-OS we use Debian 7 (Wheezy) 64bit.

regards

 

[werter]

Hi, the same errror:

INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2019-10-02 22:03:19
INFO: status = running
INFO: update VM 102: -lock backup
INFO: VM Name: eias
INFO: include disk 'virtio0' 'local-zfs:vm-102-disk-1' 40G
INFO: include disk 'virtio1' 'local-zfs:vm-102-disk-2' 80G
INFO: include disk 'virtio2' 'local-zfs:vm-102-disk-3' 120G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-102-2019_10_02-22_03_19.vma.lzo'
INFO: started backup task '6c441e98-e153-409d-8943-0e48510dfd90'
...
INFO: status: 39% (100551950336/257698037760), sparse 9% (25187852288), duration 1814, read/write 41/41 MB/s
ERROR: VM 102 qmp command 'query-backup' failed - client closed connection
INFO: aborting backup job
ERROR: VM 102 not running
ERROR: Backup of VM 102 failed - VM 102 qmp command 'query-backup' failed - client closed connection
INFO: Failed at 2019-10-02 22:33:44

pveversion -v

proxmox-ve: 6.0-2 (running kernel: 5.0.21-2-pve)
pve-manager: 6.0-7 (running version: 6.0-7/28984024)
pve-kernel-5.0: 6.0-8
pve-kernel-helper: 6.0-8
pve-kernel-5.0.21-2-pve: 5.0.21-3
pve-kernel-5.0.21-1-pve: 5.0.21-2
ceph-fuse: 14.2.4-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.12-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-8
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-65
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
openvswitch-switch: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2

I'm DON'T HAVE the problems with free space (is OK), RAM modules (try several), HDDs (SMART status all of my hdds is OK)

Guys, what's wrong with backup process in latest PVE? Why I have a problems with backup (GZIP or LZO compression - the same) ?

P.s. Try to remove vzdump.pid + vzdump.lock files in /run (only vzdump.lock exist - why this file don't removed automatically ?) and run backup again - https://forum.proxmox.com/threads/backups-fail-error-cant-aquire-lock-var-run-vzdump-lock.26088/

 

[fabian]

Hi, the same errror:

INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2019-10-02 22:03:19
INFO: status = running
INFO: update VM 102: -lock backup
INFO: VM Name: eias
INFO: include disk 'virtio0' 'local-zfs:vm-102-disk-1' 40G
INFO: include disk 'virtio1' 'local-zfs:vm-102-disk-2' 80G
INFO: include disk 'virtio2' 'local-zfs:vm-102-disk-3' 120G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-102-2019_10_02-22_03_19.vma.lzo'
INFO: started backup task '6c441e98-e153-409d-8943-0e48510dfd90'
...
INFO: status: 39% (100551950336/257698037760), sparse 9% (25187852288), duration 1814, read/write 41/41 MB/s
ERROR: VM 102 qmp command 'query-backup' failed - client closed connection
INFO: aborting backup job
ERROR: VM 102 not running
ERROR: Backup of VM 102 failed - VM 102 qmp command 'query-backup' failed - client closed connection
INFO: Failed at 2019-10-02 22:33:44

pveversion -v

proxmox-ve: 6.0-2 (running kernel: 5.0.21-2-pve)
pve-manager: 6.0-7 (running version: 6.0-7/28984024)
pve-kernel-5.0: 6.0-8
pve-kernel-helper: 6.0-8
pve-kernel-5.0.21-2-pve: 5.0.21-3
pve-kernel-5.0.21-1-pve: 5.0.21-2
ceph-fuse: 14.2.4-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.12-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-8
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-65
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
openvswitch-switch: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2

I'm DON'T HAVE the problems with free space (is OK), RAM modules (try several), HDDs (SMART status all of my hdds is OK)

Guys, what's wrong with backup process in latest PVE? Why I have a problems with backup (GZIP or LZO compression - the same) ?

P.s. Try to remove vzdump.pid + vzdump.lock files in /run (only vzdump.lock exist - why this file don't removed automatically ?) and run backup again - https://forum.proxmox.com/threads/backups-fail-error-cant-aquire-lock-var-run-vzdump-lock.26088/

please don't hijack threads from many years ago. you are likely hitting the problem described in https://forum.proxmox.com/threads/certain-vms-from-a-cluster-cannot-be-backed-up-and-managed.57016/ , please see the last few posts there.