pvestatd.pm - Use of uninitialized value $cost

[David Hooton]

I'm running 5.0-9/c7bdd872 on an HP P4500, my logs are currently filling up with the following errors:

May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.

I had an issue a while ago with 5.0 due to the CPU ID's on the P4500 not having sequential ID's, is this related?

root@bruce:~# pveversion -v
proxmox-ve: 5.0-7 (running kernel: 4.10.8-1-pve)
pve-manager: 5.0-9 (running version: 5.0-9/c7bdd872)
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.10.5-1-pve: 4.10.5-5
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.4.49-1-pve: 4.4.49-86
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.10.8-1-pve: 4.10.8-7
pve-kernel-4.4.44-1-pve: 4.4.44-84
libpve-http-server-perl: 2.0-2
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-4
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-8
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-3
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.7-500
lxcfs: 2.0.6-pve500
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
openvswitch-switch: 2.7.0-2

 

[Blais]

Hi, same problem here.

 

[drno]

Since i updated from 4.4 to 5.0, i have got the same issue

 

[fabian]

could you file a bug report at https://bugzilla.proxmox.com? thanks

 

[fabian]

should be fixed in libpve-common-perl >= 5.0-12