pvestatd halts causing status of VMs to disappear


New Member
Jul 1, 2023

I'm having problem with the status of VMs and LXCs disappearing and leaving a question mark. I've had this before on earlier releases of proxmox, but at one point on proxmox 7 it was gone, but I recently did a clean install of proxmox 8, and now it's back.

So I figured out that the pvestatd service halts without any errors logged.
It looks like reading /proc/xx/cmdline is what's halting the script.

Here's the trace:
In file pvestatd.pm:
update_status() -> remove_stale_lxc_consoles() -> PVE::LXC::find_lxc_console_pids();

In file LXC.pm "sub find_lxc_console_pids()":
$cmdline = PVE::Tools::file_read_firstline("/proc/$pid/cmdline");

In my case it halted on this pid:
# cat /proc/1429/status
Name: pve-firewall
Umask: 0022
State: D (disk sleep)

I haven't used or configured the firewall, but I've been messing around with the networking, adding a wireguard tunnel and a gretap tunnel, but I don't know if that's relevant.

Looks like halting read on /proc/*/cmdline is a common error, is it possible to add a read timeout to the read_firstline() function and have it report error instead of halting? Or check the state before trying to read it?
Last edited:


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!