Recently created 3rd node network settings missing in web UI

[obsolete]

Hello,

I recently created a 3rd node for my proxmox cluster. When I navigate to Node -> System -> Network, I do not see my vmbr0 network listed... which is strange.

If I navigate to the console (or ssh over to the box), and check the IP settings, I can see that vmbr0 exists...

If I check /etc/network/interfaces, I can see it's defined...

root@pve-node3:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.0.0.12/24
        gateway 10.0.0.1
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0

auto enxc4411e76cd81
iface enxc4411e76cd81 inet static
        address 192.168.0.3/24

Are there any suggestions on making the web UI reflect the actual configuration on the box?

 

[obsolete]

Interestingly, various elements of the web UI are slow to load, or timeout, on pve-node3.

• On the node Summary pane, the Status box doesn't load, and I get a communication failure (0) message box; the CPU usage box loads just fine though.
• If I linger on network settings, a message box with a Connection error - Timeout. message appears; same with the Certificates, DNS, Hosts, Time, and syslog settings.
• If I click through the LVM or LVM-Thin settings, a message box with a Connection error - Timeout. message appears.
• Interestingly, the Shell works just fine.

It's like real time data retrieval used to populate many of these display panes is broken..? I had issues initially joining this node (pve-node3) to the cluster. I was initially get 500 errors, where the cluster couldn't resolve the node's hostname. I fixed that by ensuring that all nodes were listed in the host file on each node.

I'm not real sure where to go from here... any advice would be most welcome.

 

[obsolete]

Nobody has encountered this issue before?

 

[obsolete]

Came across an old thread by searching for error messages I was seeing... In that older thread, someone mentioned that the pveproxy service was the cause of their issue (in their case, the service had stopped... but in my case, the service was running). Anyway, I restarted the pveproxy service, and now it seems like the node is fully functional.

Also, I feel like I should mention it because I'm not sure if it's related... but I did issue the pvecm updatecerts a little while ago... so maybe it was a combination of the two?