pvestatd

  1. A

    PVE random crash / pvestatd.service killed

    Yesterday, my PVE crashed "out of nowhere" (I did not change any configuration, issue any command or such, just normal VMs running as ever). It ran flawlessly on exactly this hardware for 2 years now. Since the first thing that happened according to journalctl -xeb-1 was, that the...
  2. L

    pvestatd keep crashing for no reason

    pvestatd service keep crashing after sepaming sdn status update error: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "(end of string)") at /usr/share/perl5/PVE/Network/SDN/Zones.pm line 201. I tested on another proxmox machine and I...
  3. S

    pvestatd halts causing status of VMs to disappear

    Hi, 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...
  4. A

    [SOLVED] [ PMX cluster ] Pool CEPH unavailable status on only one node

    Hello, On our cluster proxmox, Ceph pool "Pool_SSD" appeared to be unavailable on UI Proxmox on only one node. But we had no anomaly ( OSD Good / PG Replicat good ). We had'nt graph usage pool on this node and icons on pool was unavailable. Solv : Process pvestatd.service was running...
  5. P

    [SOLVED] Changing IP for pvestatd

    I have recently changed the IP for my HomeLab from '192.168.178.54' to '192.168.178.169'. Since doing so pvestatd still tries to connect to the old IP, which leads to a timeout and all my system info in the web interface not being accessible. Jun 25 09:55:16 pve pvestatd[1639]: lxc status...
  6. M

    Linstor Performance/Skalierungs Problem

    Guten Tag Zusammen, aktuell setzen wir ein Proxmox 6.4-4 zusammen mit Linstor 1.7.1 (DRBD 9.0.28) als verteilten Block-Storage für VM Disk-Images über 7 PVE Nodes ein. Uns ist aufgefallen, dass mit steigender Anzahl an Ressourcen und PVE-Nodes die Performance von Linstor erheblich...
  7. S

    Cluster Status Missing From External Metric Server Metrics

    Hello, recently i have deployed allot of small Proxmox VE Clusters which now have a need for monitoring. I have used Influx and Grafana to monitor Containers and VM's in the past and was very surprised to see that the External Metric Server doesn't supply any Metrics about the Cluster status...
  8. B

    pvestatd leak creates 3000+ processes, consumes all RAM & SWAP, and halts/reboots machine over a 4 hour cycle. Then repeats.

    This has occurred from the later PVE 6.1 updates (I think) and definitely all throughout PVE 6.2 (including 6.2-12) since about March 2020. Prior to this the system was rock-solid for about 1.5 years. Normal operation is ~10-12Gig usage (of 32G total). See attached picture for the cycle...
  9. Coolguy3289

    pvestatd causing unresponsive status in web GUI

    Hello, I've just added a 4th node to my existing proxmox cluster, and I'm running into an intermittent issue with the status of the node and VMs on that node turning to the gray question mark, storage stats not loading. When I run `systemctl status pvestatd` the service shows as running. When I...
  10. V

    Pvestatd won't work after deleting a lvm

    Hello, I need some help please. Today after deleting a volume from a storage array, and later the lvm from proxmox, the service pvestatd isn't working. If I enter to the web gui, I see everything greyed with question marks. When I restart the service pvestatd it works for a minute, but later...
  11. E

    [SOLVED] Unable to activate Storage ... that no longer exist

    Hi, Yesterday, 3 storage units destined to NFS backup lost connection and their status are gone. With the intention of recovering those states again, they were remounted with the only command that allowed it: umount -f -l ... what happened next, is what I show in the attached picture...
  12. D

    pvestatd and pve-firewall doesn`t start after reboot

    Recently we upgrade 5.4 to 6.1 and replace ifupdown to ifupdown2. After changes - pvestatd and pve-firewall doesn`t start after reboot, logs showing only - timeout. If 'systemctl start pvestatd' invoked by hands - service starts. Can someone help us - find the right direction to debug this ...
  13. U

    [SOLVED] Grey unknown status

    Hi, I have been having an issue with the web interface of proxmox showing my node and all vm/containers running on it as having an "unknown" status with grey ? marks. This seems to happen a few hours after every reboot of the server. Restarting pvedaemon, pveproxy, pvestatd does not seem to...
  14. B

    [SOLVED] Unable to get PID for CT on stop

    Hi. I'm running into an issue where when I try to stop a container. In my syslog I get this error: Aug 07 18:27:40 vmworld pvestatd[4024]: unable to get PID for CT 122 (not running?) Aug 07 18:27:41 vmworld pvestatd[4024]: unable to get PID for CT 122 (not running?) Aug 07 18:27:50 vmworld...
  15. M

    [TUTORIAL] Disk prevent from spinning down because of pvestatd

    Hi, you might have the problem that you want to spin down some disks, but that doesn't work as planned. I just spend 2 hours debugging the problem, and so decided to write this short tutorial. Symptom: You have multiple drives in your proxmox machines, and want some (like all HDDs) to spin down...
  16. grin

    Upgrade breaks pvestatd against CTs

    Mar 19 01:10:30 freddy pvestatd[2324627]: lxc status update error: can't open '/sys/fs/cgroup/blkio/lxc/117/ns/blkio.throttle.io_service_bytes' - No such file or directory Mar 19 01:10:34 freddy pvestatd[2324627]: lxc console cleanup error: can't open...
  17. E

    [SOLVED] pvestatd.service crashing at midnight

    Hi all, Kind of an ongoing issue that I have been dealing with. It would seem that my pvestatd.service randomly crashes at or very near midnight on one of my nodes. Sometimes this causes only the daemon to crash, other times it will cause the node to become unresponsive until hard-reboot...
  18. S

    HDD gets waken up by pvestatd

    Hello, I've got an Archival HDD installed in my system, additionally to a RAID Z-1 out of 4x 500 GB SSDs. The only issue is that the Archival HDD keeps getting waken up by pvestatd, when stopping the service it usally stays in sleep mode. Any ideas how to fix this issue? spyfly
  19. H

    pvestatd - multiple network interfaces (4.4)

    Good day, It appears that pvestatd doesn't track all the traffic on all the interfaces in the host summary page, only the "primary" interface. Any pointers how to tell it to track all/other interfaces too?
  20. E

    pve pvestatd: could not activate storage zfs error: import by numeric ID instead

    Greets. Updated and rebooted pve. Now getting logs full of these. Sparse information on the googles. Most seems more oriented to someone in the rarefied zfs guru realms. Me? I'm not even sure where to start. Help? <lots-and-lots-of-these> May 13 14:07:59 pve pvestatd[2036]: could not...

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!