[SOLVED] Every Backup task failed (Version: 4.0Beta-26/5d4a615b)

S

Sokom

Renowned Member
Aug 18, 2015
4
0
66
Hi,
our Proxmox server (Version: 4.0Beta-26/5d4a615b, installed on top of Debian Jessie 8.1) failed every backup tasks.
It said:


VMIDNAMESTATUSTIMESIZEFILENAME
101******FAILED00:00:01
00:00:010KB

[TD="colspan: 2"]Can't use string ("d06a29d7-0155-4ee0-a6a4-6739caf0"...) as a HASH ref while "strict refs" in use at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 321.[/TD]

[TD="colspan: 3, align: left"]TOTAL[/TD]


Detailed backup logs:

vzdump 101 --mode snapshot --mailto ***@***.** --compress gzip --storage /***** --quiet 1 --mailnotification always

101: ago 18 09:41:02 INFO: Starting Backup of VM 101 (qemu)
101: ago 18 09:41:02 INFO: status = running
101: ago 18 09:41:03 INFO: Use of uninitialized value $raw in pattern match (m//) at /usr/share/perl5/PVE/AccessControl.pm line 711.
101: ago 18 09:41:03 INFO: update VM 101: -lock backup
101: ago 18 09:41:03 INFO: backup mode: snapshot
101: ago 18 09:41:03 INFO: ionice priority: 7
101: ago 18 09:41:03 INFO: creating archive '/*****/dump/vzdump-qemu-101-2015_08_18-09_41_02.vma.gz'
101: ago 18 09:41:03 ERROR: Can't use string ("d06a29d7-0155-4ee0-a6a4-6739caf0"...) as a HASH ref while "strict refs" in use at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 321.
101: ago 18 09:41:03 INFO: aborting backup job
101: ago 18 09:41:03 INFO: Use of uninitialized value $raw in pattern match (m//) at /usr/share/perl5/PVE/AccessControl.pm line 711.
101: ago 18 09:41:03 ERROR: Backup of VM 101 failed - Can't use string ("d06a29d7-0155-4ee0-a6a4-6739caf0"...) as a HASH ref while "strict refs" in use at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 321.


It happened to someone else?

Thanks
Regards

Sokom
 
Last edited:
t.lamprecht said:
Please upgrade to the newest version with
Code: 
apt-get update
apt-get dist-upgrade

This bug was in the qemu-sever package and is already fixed.
Click to expand...

Sorry, but:

# apt-get dist-upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Eseguito
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.

# cat /etc/apt/sources.list.d/pve-enterprise.list
# changed to pvetest, because this is a beta release
deb http://download.proxmox.com/debian jessie pvetest
#deb https://enterprise.proxmox.com/debian jessie pve-enterprise

# dpkg -l | grep qemu-ser
ii qemu-server 4.0-15 amd64 Qemu Server Tools


The system seems to be already updated.

Since we did a dist-upgrade yesterday, maybe the system required a complete reboot to apply the fix?
Thanks
Regards

Sokom
 
Ok the version should be good, have you qemu 2.4 (it's in the pve-qemu-kvm package) installed or 2.3? It looks like it 2.3, try to install pve-qemu-kvm 2.4-1.
Please post the output of pveversion -v
 
Last edited:
t.lamprecht said:
Ok the version should be good, have you qemu 2.4 (it's in the pve-qemu-kvm package) installed or 2.3? It looks like it 2.3, try to install pve-qemu-kvm 2.4-1.
Please post the output of pveversion -v
Click to expand...

We have 2.4-1.
This is our output::

# pveversion -v
proxmox-ve: 4.0-7 (running kernel: 3.19.8-1-pve)
pve-manager: 4.0-26 (running version: 4.0-26/5d4a615b)
pve-kernel-3.19.8-1-pve: 3.19.8-3
pve-kernel-4.1.3-1-pve: 4.1.3-7
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-14
qemu-server: 4.0-15
pve-firmware: 1.1-6
libpve-common-perl: 4.0-14
libpve-access-control: 4.0-6
libpve-storage-perl: 4.0-13
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-1
pve-container: 0.9-7
pve-firewall: 2.0-6
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-4
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2


Thanks
Regards
Sokom
 
Ok, strange. I could reproduce your error, but only if I installed pve-qemu-kvm 2.3-6 with qemu-server 4.0-15.

With the same versions as yours everything works like a charm:
proxmox-ve: 4.0-8 (running kernel: 4.1.3-1-pve)
pve-manager: 4.0-28 (running version: 4.0-28/74692ece)
pve-kernel-3.19.8-1-pve: 3.19.8-5
pve-kernel-4.1.3-1-pve: 4.1.3-8
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-15
qemu-server: 4.0-15
pve-firmware: 1.1-6
libpve-common-perl: 4.0-14
libpve-access-control: 4.0-6
libpve-storage-perl: 4.0-14
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-1
pve-container: 0.9-9
pve-firewall: 2.0-6
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-6
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
Click to expand...

Normally these two packages don't require an reboot, but it won't hurt.
Please report back if that solved your problems.
 
Ok, now I know the problem, restart the VM's which where started before the dist-upgrade and your good. They're running still with the old pve-qemu-kvm and so are incompatible with the new qemu-server.

Reboot of the whole node should fix that also.
 
[SOLVED] Re: Every Backup task failed (Version: 4.0Beta-26/5d4a615b)

t.lamprecht said:
Ok, now I know the problem, restart the VM's which where started before the dist-upgrade and your good. They're running still with the old pve-qemu-kvm and so are incompatible with the new qemu-server.

Reboot of the whole node should fix that also.
Click to expand...


Ok, I restarted a VM which were started before dist-upgrade: Backup is now working!
Thanks for support.
Regards

Sokom
 
Last edited:
You must log in or register to reply here.
Top Bottom