Really Strange Behaviour in VE WebUI

[soopman]

Hi All,

I have been having some really strange behaviour in my VE webui that is driving me nuts. For a couple of months now the names of my Containers and VM's do not show up in the UI and I just cannot figure it out. I am now reaching out to the wider community to see if it is a know problem or someone can kindly help me to figure it out.

Thank you

 

[zahnfee]

Happened to me once when /etc/hosts was incorrect (hostname --ip-address)

 

[UdoB]

the names of my Containers and VM's do not show up in the UI

Very first guess: systemctl status pveproxy.service. If the output does not contain "active (running)" just (re-)start it...

"For a couple of months now..." - really? Probably it is difficult to say what you did back then...

 

[soopman]

Very first guess: systemctl status pveproxy.service. If the output does not contain "active (running)" just (re-)start it...

"For a couple of months now..." - really? Probably it is difficult to say what you did back then...

It is running. I have tried all the possible cases I found online but without success.

● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-04-24 18:53:50 CEST; 1 week 2 days ago
Process: 3760666 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
Main PID: 1869 (pveproxy)
Tasks: 4 (limit: 76687)
Memory: 195.3M
CPU: 17min 34.646s
CGroup: /system.slice/pveproxy.service
├─ 1869 pveproxy
├─827915 "pveproxy worker"
├─831858 "pveproxy worker"
└─836959 "pveproxy worker"

May 04 12:57:53 elite pveproxy[1869]: starting 1 worker(s)
May 04 12:57:53 elite pveproxy[1869]: worker 827915 started
May 04 13:00:15 elite pveproxy[770347]: worker exit
May 04 13:00:15 elite pveproxy[1869]: worker 770347 finished
May 04 13:00:15 elite pveproxy[1869]: starting 1 worker(s)
May 04 13:00:15 elite pveproxy[1869]: worker 831858 started
May 04 13:03:29 elite pveproxy[753634]: worker exit
May 04 13:03:29 elite pveproxy[1869]: worker 753634 finished
May 04 13:03:29 elite pveproxy[1869]: starting 1 worker(s)
May 04 13:03:29 elite pveproxy[1869]: worker 836959 started

 

[UdoB]

Okay.

It should listen on port 8006. Does it? On my system I can succesfully check:

ss -tlpn | grep 8006
LISTEN 0      4096               *:8006             *:*    users:(("pveproxy worker",pid=3712440,fd=6),("pveproxy worker",pid=3711962,fd=6),("pveproxy worker",pid=3707704,fd=6),("pveproxy",pid=2254,fd=6))

Then, as already mentioned by zahnfee, name resolution must fit reality. "host elite", "hostname", "cat /etc/hosts", "ls -Al /etc/pve/local" ... all outputs must be consistent.

 

[soopman]

~# ss -tlpn | grep 8006
LISTEN 0 4096 *:8006 *:* users("pveproxy worker",pid=907391,fd=6),("pveproxy worker",pid=906508,fd=6),("pveproxy worker",pid=905602,fd=6),("pveproxy",pid=1869,fd=6))

I have checked the hosts file and everything in there look correct.

 

[bbgeek17]

If the "proxy" was not running, there would be no GUI at all.

The question marks likely indicate that "pvestatd" is not responding properly. There could be many causes: slow storage, non-accessible storage, bug, etc.
Recently users reported external factors, like a non-responsive metrics server causing general system misbehavior.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[soopman]

If the "proxy" was not running, there would be no GUI at all.

The question marks likely indicate that "pvestatd" is not responding properly. There could be many causes: slow storage, non-accessible storage, bug, etc.
Recently users reported external factors, like a non-responsive metrics server causing general system misbehavior.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for your input. I have just an NFS connection to my NAS for backups but most of the time it is actually not being used. Interestingly, I have removed the NFS share and rebooted. Everything is working again. Super strange.

My sincere gratitude to everyone who gave me insights. This is a truly awesome community. I appreciate you all