[SOLVED] Error when running 'pvesh get'

stra4d

Well-Known Member
Mar 1, 2012
80
0
46
When checking the current status of a VM via 'pvesh get', have been getting an error after a recent update. Anybody else see this?

Command: /usr/bin/pvesh get /nodes/<servername>/qemu/101/status/current

Results:
Code:
Invalid conversion in sprintf: "%.H" at /usr/share/perl5/PVE/Format.pm line 75.
Invalid conversion in sprintf: "%.H" at /usr/share/perl5/PVE/Format.pm line 75.
┌───────────┬─────────────────────────────┐
│ key       │ value                       │
╞═══════════╪═════════════════════════════╡
│ agent     │ 1                           │
├───────────┼─────────────────────────────┤
│ cpus      │ 4                           │
├───────────┼─────────────────────────────┤
│ ha        │ {"managed":0}               │
├───────────┼─────────────────────────────┤
│ maxdisk   │ %.HASH(0x562b37a5aed8)f GiB │
├───────────┼─────────────────────────────┤
│ maxmem    │ %.HASH(0x562b37a5aed8)f GiB │
├───────────┼─────────────────────────────┤
│ name      │ theserver                   │
├───────────┼─────────────────────────────┤
│ pid       │ 1295                        │
├───────────┼─────────────────────────────┤
│ qmpstatus │ running                     │
├───────────┼─────────────────────────────┤
│ status    │ running                     │
├───────────┼─────────────────────────────┤
│ uptime    │ 2d 8h 45m 29s               │
├───────────┼─────────────────────────────┤
│ vmid      │ 101                         │
└───────────┴─────────────────────────────┘

pverversion:
Code:
~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.101-1-pve)
pve-manager: 6.3-4 (running version: 6.3-4/0a38c56f)
pve-kernel-5.4: 6.3-6
pve-kernel-helper: 6.3-6
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.4.98-1-pve: 5.4.98-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-5
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-2
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve2
 
Ok great - we were up to date when we saw this last week, but seems to have been updates since. Sorry - should have checked that first Thanks.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!