All containers and disks show as question marks

mkyb14

Well-Known Member
Mar 17, 2017
58
1
48
40
Happened after updating from the GUI the packages.... no idea why and nothing I've found about restarting services has helped.
Some screenshots of the GUI below

Reboot didn't fix and restarting services from other forum posts didn't fix it either.
 

Attachments

  • Screenshot 2022-12-20 at 5.29.29 PM.png
    Screenshot 2022-12-20 at 5.29.29 PM.png
    244.2 KB · Views: 21
  • Screenshot 2022-12-20 at 5.29.02 PM.png
    Screenshot 2022-12-20 at 5.29.02 PM.png
    182.6 KB · Views: 19
  • Screenshot 2022-12-20 at 5.27.46 PM.png
    Screenshot 2022-12-20 at 5.27.46 PM.png
    187.5 KB · Views: 18
Please provide the full output in code-tags of:
  • systemctl status pvestatd.service
  • pvesm status
Also check your syslog.
 
Code:
root@pve:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-12-20 17:24:05 PST; 16h ago
    Process: 1984770 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
   Main PID: 1984773 (pvestatd)
      Tasks: 1 (limit: 154342)
     Memory: 81.7M
        CPU: 15min 52.297s
     CGroup: /system.slice/pvestatd.service
             └─1984773 pvestatd

Dec 21 10:00:25 pve pvestatd[1984773]: lxc status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:25 pve pvestatd[1984773]: storage status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:35 pve pvestatd[1984773]: node status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:35 pve pvestatd[1984773]: qemu status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:35 pve pvestatd[1984773]: lxc status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:35 pve pvestatd[1984773]: storage status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:45 pve pvestatd[1984773]: node status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:45 pve pvestatd[1984773]: qemu status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:45 pve pvestatd[1984773]: lxc status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
Dec 21 10:00:45 pve pvestatd[1984773]: storage status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/ExtMetric.pm line 21.
root@pve:~#
 

Attachments

  • Screenshot 2022-12-21 at 10.02.10 AM.png
    Screenshot 2022-12-21 at 10.02.10 AM.png
    30 KB · Views: 7
I had installed a lxc grafana image, but have since uninstalled it and purged the info. rebooted. Still throwing the same error.
 
Can you please provide the full output in code-tags of: cat /etc/pve/status.cfg
 
root@pve:~# cat /etc/pve/status.cfg
influxdb:
server 192.168.22.21
port 8089
 
As you can see, there is still a config.
Since this file does not exist on my PVE-hosts at all, I would suggest to rename or move (as a backup) or even delete it and reboot the PVE-host afterwards again.
 
that fixed it. So is PVE looking at that directory for a status.cfg and if ones there it breaks metrics?
 

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!