The problem with backup an start VM

[Nychary]

Hi!

I have a problem with backup and starting a VM after a backup failure.

My log:

INFO: starting new backup job: vzdump 103 --mailnotification always --quiet 1 --mode stop --storage Ev_backup --compress gzip
INFO: Starting Backup of VM 103 (qemu)
INFO: status = running
INFO: update VM 103: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: test_vm
INFO: include disk 'virtio1' 'local-zfs:vm-103-disk-2' 500G
INFO: stopping vm
INFO: creating archive '/mnt/pve/Ev_backup/dump/vzdump-qemu-103-2021_12_22-22_15_02.vma.gz'
INFO: starting kvm to execute backup task
malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "(end of string)") at /usr/share/perl5/PVE/Tools.pm line 949, <GEN95> chunk 1.
ERROR: unable to connect to VM 103 qmp socket - No such file or directory
INFO: aborting backup job
ERROR: VM 103 not running
INFO: restarting vm
INFO: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "(end of string)") at /usr/share/perl5/PVE/Tools.pm line 949, <GEN26> chunk 1.
INFO: vm is online again after 18 seconds
ERROR: Backup of VM 103 failed - unable to connect to VM 103 qmp socket - No such file or directory
INFO: Backup job finished with errors

I have found the similar issue in this forum (https://forum.proxmox.com/threads/qm-start-id-returns-malformed-json-string.44541/) but I don't want to restart my node. Maybe there are other ways to fix this?

Thank you.

 

[oguz]

hi,

which version are you running? pveversion -v

also could you post the VM config as well? qm config VMID

 

[Nychary]

hi,

which version are you running? pveversion -v

also could you post the VM config as well? qm config VMID

pveversion -v

undefinedpveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-1
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-3
pve-firewall: 3.0-8
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.8-pve1~bpo9

qm config 103

undefinedroot@perseus:/home/nifnif# qm config 103
agent: 1
balloon: 0
boot: cdn
bootdisk: virtio1
cores: 17
cpu: host
memory: 100000
name: Scorpius
net0: e1000=BE:47:84:38:E9:82,bridge=vmbr0
net1: virtio=DE:75:15:0E:70:38,bridge=vmbr0
numa: 0
onboot: 1
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=e97b1fa4-e953-493d-82a1-e72a673f28b6
sockets: 2
virtio1: local-zfs:vm-103-disk-2,cache=writeback,size=500G
root@perseus:/home/nifnif#

 

[oguz]

proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)

PVE5 is EOL, we suggest you upgrade to PVE6 [0] then PVE7[1] to get the latest features, bugfixes and security upgrades

[0]: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
[1]: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0