[SOLVED] VM Status "Unknown" - Grey Question Mark

J

jjgg

Member
Jul 10, 2021
5
0
6
Fresh install of PVE7 iso, upgraded using pve-no-subscription repo this morning.

Getting "Status: Unknown" on a VM, which is just a fresh Ubuntu 20LTS:

1625953467408.png

Storage is reporting fine, other things reporting fine. Created a second VM, same issue.

Did a search, found this thread, restarting those services made no difference.

FYI:
Code: 
root@pmhost0x:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-9 (running version: 7.0-9/228c9caa)
pve-kernel-helper: 7.0-4
pve-kernel-5.11: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve6
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-8
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-10
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1
root@pmhost0x:~#

Code: 
root@pmhost0x:~# systemctl status pve*
● pve-firewall.service - Proxmox VE firewall
     Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:36 NZST; 12h left
    Process: 1265 ExecStartPre=/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy (code=exited, status=0/SUCCESS)
    Process: 1268 ExecStartPre=/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy (code=exited, status=0/SUCCESS)
    Process: 1269 ExecStartPre=/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy (code=exited, status=0/SUCCESS)
    Process: 1270 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=0/SUCCESS)
   Main PID: 1273 (pve-firewall)
      Tasks: 1 (limit: 193300)
     Memory: 85.4M
        CPU: 27.182s
     CGroup: /system.slice/pve-firewall.service
             └─1273 pve-firewall

Jul 11 21:49:32 pmhost0x systemd[1]: Starting Proxmox VE firewall...
Jul 11 21:49:36 pmhost0x pve-firewall[1273]: starting server
Jul 11 21:49:36 pmhost0x systemd[1]: Started Proxmox VE firewall.

● pve-daily-update.timer - Daily PVE download activities
     Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; vendor preset: enabled)
     Active: active (waiting) since Sun 2021-07-11 21:49:29 NZST; 12h left
    Trigger: Mon 2021-07-12 04:59:55 NZST; 19h left
   Triggers: ● pve-daily-update.service

Jul 11 21:49:29 pmhost0x systemd[1]: Started Daily PVE download activities.

● pve-storage.target - PVE Storage Target
     Loaded: loaded (/lib/systemd/system/pve-storage.target; static)
     Active: active since Sun 2021-07-11 21:49:29 NZST; 12h left

Jul 11 21:49:29 pmhost0x systemd[1]: Reached target PVE Storage Target.

● pvebanner.service - Proxmox VE Login Banner
     Loaded: loaded (/lib/systemd/system/pvebanner.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sun 2021-07-11 21:49:28 NZST; 12h left
    Process: 834 ExecStart=/usr/bin/pvebanner (code=exited, status=0/SUCCESS)
   Main PID: 834 (code=exited, status=0/SUCCESS)
        CPU: 587ms

Jul 11 21:49:24 pmhost0x systemd[1]: Starting Proxmox VE Login Banner...
Jul 11 21:49:28 pmhost0x systemd[1]: Finished Proxmox VE Login Banner.

● pvefw-logger.service - Proxmox VE firewall logger
     Loaded: loaded (/lib/systemd/system/pvefw-logger.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:24 NZST; 12h left
    Process: 835 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS)
   Main PID: 858 (pvefw-logger)
      Tasks: 2 (limit: 193300)
     Memory: 1.6M
        CPU: 399ms
     CGroup: /system.slice/pvefw-logger.service
             └─858 /usr/sbin/pvefw-logger

Jul 11 21:49:24 pmhost0x systemd[1]: Starting Proxmox VE firewall logger...
Jul 11 21:49:24 pmhost0x pvefw-logger[858]: starting pvefw logger
Jul 11 21:49:24 pmhost0x systemd[1]: Started Proxmox VE firewall logger.

● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:32 NZST; 12h left
    Process: 1253 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 1259 (pmxcfs)
      Tasks: 7 (limit: 193300)
     Memory: 58.8M
        CPU: 5.101s
     CGroup: /system.slice/pve-cluster.service
             └─1259 /usr/bin/pmxcfs

Jul 11 09:38:31 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:39:12 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:39:23 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:46:03 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:46:03 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:46:03 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:46:09 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:47:21 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:47:23 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate
Jul 11 09:47:23 pmhost0x pmxcfs[1259]: [main] notice: ignore duplicate

● pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:36 NZST; 12h left
    Process: 1267 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
   Main PID: 1272 (pvestatd)
      Tasks: 1 (limit: 193300)
     Memory: 105.0M
        CPU: 36.292s
     CGroup: /system.slice/pvestatd.service
             └─1272 pvestatd

Jul 11 21:49:32 pmhost0x systemd[1]: Starting PVE Status Daemon...
Jul 11 21:49:36 pmhost0x pvestatd[1272]: starting server
Jul 11 21:49:36 pmhost0x systemd[1]: Started PVE Status Daemon.

● pve-guests.service - PVE guests
     Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sun 2021-07-11 21:49:42 NZST; 12h left
    Process: 1317 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
    Process: 1318 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=0/SUCCESS)
   Main PID: 1318 (code=exited, status=0/SUCCESS)
        CPU: 1.455s

Jul 11 21:49:41 pmhost0x systemd[1]: Starting PVE guests...
Jul 11 21:49:42 pmhost0x pve-guests[1318]: <root@pam> starting task UPID:pmhost0x:00000527:00000E09:60EABEB6:startall::root@pam:
Jul 11 21:49:42 pmhost0x pve-guests[1318]: <root@pam> end task UPID:pmhost0x:00000527:00000E09:60EABEB6:startall::root@pam: OK
Jul 11 21:49:42 pmhost0x systemd[1]: Finished PVE guests.

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 09:39:14 NZST; 8min ago
    Process: 9659 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 9662 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 9663 (pveproxy)
      Tasks: 4 (limit: 193300)
     Memory: 205.8M
        CPU: 7.101s
     CGroup: /system.slice/pveproxy.service
             ├─9663 pveproxy
             ├─9664 pveproxy worker
             ├─9665 pveproxy worker
             └─9666 pveproxy worker

Jul 11 09:39:12 pmhost0x systemd[1]: Starting PVE API Proxy Server...
Jul 11 09:39:14 pmhost0x pveproxy[9663]: starting server
Jul 11 09:39:14 pmhost0x pveproxy[9663]: starting 3 worker(s)
Jul 11 09:39:14 pmhost0x pveproxy[9663]: worker 9664 started
Jul 11 09:39:14 pmhost0x pveproxy[9663]: worker 9665 started
Jul 11 09:39:14 pmhost0x pveproxy[9663]: worker 9666 started
Jul 11 09:39:14 pmhost0x systemd[1]: Started PVE API Proxy Server.

● pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon
     Loaded: loaded (/lib/systemd/system/pve-lxc-syscalld.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:25 NZST; 12h left
   Main PID: 873 (pve-lxc-syscall)
      Tasks: 33 (limit: 193300)
     Memory: 2.5M
        CPU: 6ms
     CGroup: /system.slice/pve-lxc-syscalld.service
             └─873 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock

Jul 11 21:49:25 pmhost0x systemd[1]: Starting Proxmox VE LXC Syscall Daemon...
Jul 11 21:49:25 pmhost0x systemd[1]: Started Proxmox VE LXC Syscall Daemon.

● pvesr.timer - Proxmox VE replication runner
     Loaded: loaded (/lib/systemd/system/pvesr.timer; enabled; vendor preset: enabled)
     Active: active (waiting) since Sun 2021-07-11 21:49:29 NZST; 12h left
    Trigger: Sun 2021-07-11 09:48:00 NZST; 489ms left
   Triggers: ● pvesr.service

Jul 11 21:49:29 pmhost0x systemd[1]: Started Proxmox VE replication runner.

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:38 NZST; 12h left
    Process: 1266 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1298 (pvedaemon)
      Tasks: 6 (limit: 193300)
     Memory: 1.4G
        CPU: 1min 8.553s
     CGroup: /system.slice/pvedaemon.service
             ├─ 1298 pvedaemon
             ├─ 1299 pvedaemon worker
             ├─ 1300 pvedaemon worker
             ├─ 1301 pvedaemon worker
             ├─10862 task UPID:pmhost0x:00002A6E:00057956:60EA156B:vncshell::root@pam:
             └─10863 /usr/bin/termproxy 5901 --path /nodes/pmhost0x --perm Sys.Console -- /bin/login -f root

Jul 11 09:46:03 pmhost0x pvedaemon[10604]: start VM 101: UPID:pmhost0x:0000296C:00055A44:60EA151B:qmstart:101:root@pam:
Jul 11 09:46:03 pmhost0x pvedaemon[10590]: <root@pam> starting task UPID:pmhost0x:0000296C:00055A44:60EA151B:qmstart:101:root@pam:
Jul 11 09:46:03 pmhost0x pvedaemon[1300]: <root@pam> end task UPID:pmhost0x:0000295E:00055A1D:60EA151B:qmcreate:101:root@pam: OK
Jul 11 09:46:09 pmhost0x pvedaemon[10705]: starting vnc proxy UPID:pmhost0x:000029D1:00055CAE:60EA1521:vncproxy:101:root@pam:
Jul 11 09:46:09 pmhost0x pvedaemon[1300]: <root@pam> starting task UPID:pmhost0x:000029D1:00055CAE:60EA1521:vncproxy:101:root@pam:
Jul 11 09:47:21 pmhost0x pvedaemon[1300]: <root@pam> end task UPID:pmhost0x:000029D1:00055CAE:60EA1521:vncproxy:101:root@pam: OK
Jul 11 09:47:23 pmhost0x pvedaemon[10862]: starting termproxy UPID:pmhost0x:00002A6E:00057956:60EA156B:vncshell::root@pam:
Jul 11 09:47:23 pmhost0x pvedaemon[1300]: <root@pam> starting task UPID:pmhost0x:00002A6E:00057956:60EA156B:vncshell::root@pam:
Jul 11 09:47:23 pmhost0x pvedaemon[1299]: <root@pam> successful auth for user 'root@pam'
Jul 11 09:47:23 pmhost0x login[10867]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)

● pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon
     Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:39 NZST; 12h left
    Process: 1302 ExecStart=/usr/sbin/pve-ha-crm start (code=exited, status=0/SUCCESS)
   Main PID: 1306 (pve-ha-crm)
      Tasks: 1 (limit: 193300)
     Memory: 89.8M
        CPU: 1.337s
     CGroup: /system.slice/pve-ha-crm.service
             └─1306 pve-ha-crm

Jul 11 21:49:38 pmhost0x systemd[1]: Starting PVE Cluster HA Resource Manager Daemon...
Jul 11 21:49:39 pmhost0x pve-ha-crm[1306]: starting server
Jul 11 21:49:39 pmhost0x pve-ha-crm[1306]: status change startup => wait_for_quorum
Jul 11 21:49:39 pmhost0x systemd[1]: Started PVE Cluster HA Resource Manager Daemon.

● pve-ha-lrm.service - PVE Local HA Resource Manager Daemon
     Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-07-11 21:49:41 NZST; 12h left
    Process: 1312 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=0/SUCCESS)
   Main PID: 1316 (pve-ha-lrm)
      Tasks: 1 (limit: 193300)
     Memory: 89.5M
        CPU: 1.582s
     CGroup: /system.slice/pve-ha-lrm.service
             └─1316 pve-ha-lrm

Jul 11 21:49:40 pmhost0x systemd[1]: Starting PVE Local HA Resource Manager Daemon...
Jul 11 21:49:41 pmhost0x pve-ha-lrm[1316]: starting server
Jul 11 21:49:41 pmhost0x pve-ha-lrm[1316]: status change startup => wait_for_agent_lock
Jul 11 21:49:41 pmhost0x systemd[1]: Started PVE Local HA Resource Manager Daemon.

● pvenetcommit.service - Commit Proxmox VE network changes
     Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sun 2021-07-11 21:49:24 NZST; 12h left
    Process: 837 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS)
    Process: 839 ExecStartPre=/bin/mv /etc/network/interfaces.new /etc/network/interfaces (code=exited, status=1/FAILURE)
    Process: 846 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
   Main PID: 846 (code=exited, status=0/SUCCESS)
        CPU: 4ms

Jul 11 21:49:24 pmhost0x systemd[1]: Starting Commit Proxmox VE network changes...
Jul 11 21:49:24 pmhost0x mv[839]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory
Jul 11 21:49:24 pmhost0x systemd[1]: Finished Commit Proxmox VE network changes.
 
Hi,

just as an Idea, did you already reboot the Host? Actually i have no other glue.


cheers
 
Yes, after I switched to the pve-no-subscription repo it suggested rebooting due to new kernel, so I did then. I haven't rebooted since I created the VMs.
 
TheGrandWazoo said:
Descobri que o serviço pvestatd não estava funcionando após uma atualização de 6.4-13 para 7.0-11. Apenas fiz um 'reinício do pvestatd' e as marcas de perguntas cinzas se transformaram em ícones verdes.
Não sei por que isso aconteceu, mas parece bem agora.
Click to expand...
Essa solução funcionou pra mim.
 
TheGrandWazoo said:
I found that the pvestatd service was not running after a 6.4-13 to 7.0-11 upgrade. Just did a 'pvestatd restart' and the grey questions marks turned to the green icons.
Not sure why this happened but it seems fine now.
Click to expand...
same issue here with pve-manager/7.4-15/ systemctl status showed:
root@pve-71:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Thu 2023-07-06 20:25:59 CEST; 22h ago
Process: 1567684 ExecReload=/usr/bin/pvestatd restart (code=exited, status=0/SUCCESS)
Main PID: 3860 (code=killed, signal=SEGV)
CPU: 1d 7h 22min 59.719s

Jun 29 23:25:27 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jun 30 23:25:30 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jul 01 23:25:40 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jul 02 23:25:50 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jul 03 23:26:00 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jul 04 23:26:00 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jul 05 23:26:00 pve-71 pvestatd[3860]: auth key pair too old, rotating..
Jul 06 20:25:59 pve-71 systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
Jul 06 20:25:59 pve-71 systemd[1]: pvestatd.service: Failed with result 'signal'.
Jul 06 20:25:59 pve-71 systemd[1]: pvestatd.service: Consumed 1d 7h 22min 59.719s CPU time.

systemctl start pvestatd.service
problem solved
you saved my day ! THANKS
 
  • Like
Reactions: ibbs
FYI, not sure why, but after 2 reboots, the grey question mark issue is resolved. Proxmox 7.4-17.
 
type this command #systemctl status pve* if your pvestatd.service stopped just start your pvestatd.service using this command #systemctl start pvestatd.service and refresh the page it will solve your problem.
 
Posting just in case this helps someone in the future. I had this issue with all VMs showing status unknown. I followed the direction of @Rajankumar and received the following errors:

May 13 09:43:04 pmx01 pvestatd[2413]: node status update error: couldn't create carbon socket [grafana]:2003 - Connection timed out
May 13 09:43:05 pmx01 pvestatd[2413]: qemu status update error: couldn't create carbon socket [grafana]:2003 - Connection timed out
May 13 09:43:06 pmx01 pvestatd[2413]: lxc status update error: couldn't create carbon socket [grafana]:2003 - Connection timed out
May 13 09:43:07 pmx01 pvestatd[2413]: storage status update error: couldn't create carbon socket [grafana]:2003 - Connection timed out

I had a defunct metric server configuration pointing to a grafana instance that was offline. Once I removed the bad Metric server configuration and restarted pvestatd, the issue was resolved.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back