qm list returns a lot of errors on /usr/share/perl5/PVE/QemuServer.pm line 894

kawarmc

New Member
Jun 15, 2009
28
3
3
I have a three node setup and in two of them, when I run "qm list" from the command line I get this errors:

Code:
~# qm list
      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID       
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "360718336,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "1073754112,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "436207616,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "943714304,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "396353536,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "54534144,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "94380032,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "70512640,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "4190208,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "33554432,00" isn't numeric in division (/) at /usr/share/perl5/PVE/QemuServer.pm line 894.
       104 Procesos0-64         running    3500              32.00 3928      
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "360718336,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "1073754112,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "436207616,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "943714304,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "396353536,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "54534144,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "94380032,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "70512640,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "4190208,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "23068672,00" isn't numeric in division (/) at /usr/share/perl5/PVE/QemuServer.pm line 894.
       106 Caballo-PDC          running    2048              22.00 24800     
       107 Firewall2            running    512                0.00 8540      
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "360718336,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "1073754112,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "436207616,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "943714304,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "396353536,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
Argument "524296192,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm line 1767.
The output continues for every VM on the node.

On the third node the output is as expected.

Any advice with this? I didn't try to reboot the machines, I'm a bit scared of doing it in case the VMs don't reboot properly.
 
pls post the output of:

Code:
pveversion -v
 
I'm sorry.

Code:
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.27-1pve1
vzdump: 1.2-13
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
 
list is not complete, how did you install?

run apt-get update and apt-get install proxmox-ve-2.6.32
 
I installed this 2 nodes about 2 years ago, and after installation, several upgrades where performed (apt-get update; apt-get upgrade).

Everything has been running smooth until yesterday. Nothing special was done yesterday. I noticed the error because I begun yesterday to code a script to replicate the vmdump backup files to an offsite location and I run qm list to determine how many VMs do I have and it returned those errors.

The script to sync the files to an offsite location has nothing to do with pve nor does it use pve infrastructure at all. It just reads the output from qm list to know how the virtual machines defined on the node and look for their backup file on the backup path.

I'll upgrade again both nodes as soon as possible...
Is it better to use aptitude safe-upgrade or apt-get upgrade?
 
...
Is it better to use aptitude safe-upgrade or apt-get upgrade?

makes most times no big difference, in any case read the output of the tools and check the results. aptitude is the newer tool.
 
this is wierd.

After a few days the problem has disappeared by itself.

Now, the output of qm list is as it should be. I have done no upgrade nor any reconfiguration, there is not even new VMs created, nothing has been touched, and the problem seems fixed...

I guess it's not, but...
 
this is wierd.

After a few days the problem has disappeared by itself.

unfortunately bugs does not get fixed automatically so something must be different now.

Now, the output of qm list is as it should be. I have done no upgrade nor any reconfiguration, there is not even new VMs created, nothing has been touched, and the problem seems fixed...

I guess it's not, but...
 
Hello,

Unfortunately, I have the same error.

When I perform a backup with vzdump on the remote ssh console. Including a entire virtual machine, including the second hard disk (LVM Storage in proxmox) (the VM is not active - shut down).
in proxmox:
Code:
 vzdump --compress --stop --dumpdir smeserver/ 103
...
INFO: adding '/var/lib/vz/images/103/vm-103-disk-1.qcow2' to archive ('vm-disk-virtio0.qcow2')
INFO: adding '/dev/platte2/vm-103-disk-1' to archive ('vm-disk-virtio1.raw')
...

I have a lot of errors like:
Code:
NFO: backup mode: stop
INFO: ionice priority: 7
Argument "1953513472,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm
line 1777.
Argument "779108352,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm
line 1777.
Argument "1952985088,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm
line 1777.
Argument "4186112,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm
line 1777.
and some
Code:
Argument "650117120,00" isn't numeric in division (/) at /usr/share/perl5/PVE/QemuServer.pm line 894.
Here I found a similar error (but it dosen't help me)
http://osdir.com/ml/debian-bugs-dist/2010-06/msg08489.html
You have to look in the text file.

In the file '/usr/share/perl5/PVE/Storage.pm' the code in line 1777 is:
Code:
1767 
1768     my $vgs = {};
1769     run_command ($cmd, outfunc => sub {
1770         my $line = shift;
1771 
1772         $line =~ s/^\s+//;
1773         $line =~ s/\s+$//;
1774 
1775         my ($name, $size, $free) = split (':', $line);
1776 
1777         $vgs->{$name} = { size => int ($size), free => int ($free) };
1778     });
1779

Version
Code:
proxmox:/usr/share/perl5/PVE# vim Storage.pm 
proxmox:/usr/share/perl5/PVE# pveversion -v
pve-manager: 1.8-19 (pve-manager/1.8/6379)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.35: 1.8-13
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.35-2-pve: 2.6.35-13
qemu-server: 1.1-31
pve-firmware: 1.0-12
libpve-storage-perl: 1.0-18
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-15
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

The backup finished but I can not say it is okay

EDIT:
I dry a new backup without vzdump options
Code:
 vzdump 103
with the same errors

regards
maxprox
 
Last edited:
Code:
Argument "1953513472,00" isn't numeric in int at /usr/share/perl5/PVE/Storage.pm
line 1777.

What kind of locale do you use? What is the output of:

# LANG=C vgs --separator ':' --noheadings --units k --unbuffered --nosuffix --options vg_name,vg_size,vg_free
 
What kind of locale do you use? What is the output of:
# LANG=C vgs --separator ':' --noheadings --units k --unbuffered --nosuffix --options vg_name,vg_size,vg_free
Code:
proxmox:~# LANG=C vgs --separator ':' --noheadings --units k --unbuffered --nosuffix --options vg_name,vg_size,vg_free 
  platte2:1953513472,00:779108352,00
  pve:1952985088,00:4186112,00
proxmox:~#

EDIT:
and locale:
Code:
proxmox:~# locale
LANG=de_DE.UTF-8                                                                              
LC_CTYPE="de_DE.UTF-8"                                                                        
LC_NUMERIC=de_DE.UTF-8                                                                        
LC_TIME="de_DE.UTF-8"                                                                         
LC_COLLATE="de_DE.UTF-8"                                                                      
LC_MONETARY=de_DE.UTF-8                                                                       
LC_MESSAGES="de_DE.UTF-8"                                                                     
LC_PAPER=de_DE.UTF-8                                                                          
LC_NAME="de_DE.UTF-8"                                                                         
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=
proxmox:~#
 
Last edited:
OK; I guess I found the bug - please can you test my fix:

# wget ftp://download.proxmox.com/debian/d...nary-amd64/libpve-storage-perl_1.0-19_all.deb
# dpkg -i libpve-storage-perl_1.0-19_all.deb

EDIT:

Hello Dietmar,

YES! It works! Thank You!
Much better without the error messages. ;-)
Code:
proxmox:/opt/patch# qm list
      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID       
       102 zentyal-vm           stopped    2048              32.00 0         
       103 SME_Server_V2     stopped    1024              22.00 0         
       107 SME-Sever            stopped    1024              92.00 0         
...
And also vzdump now runs without error.
Is there something I should understand? Or can I just be happy;-)

Thank you Dietmar!
 
Last edited: