PVE node on managed switch VLAN partially working

lpallard

Renowned Member
Mar 22, 2014
99
5
73
Sorry for those who may have read this post just before I resolved my issue with VLANs... Its not irrelevant to the issue below.

Hello, I changed the static IP of my PVE node by modifying /etc/network/interfaces and /etc/hosts and /etc/resolv.conf and AFAIK everything seems OK (I can now access the WebUI and SSH to the node).

From the node (via SSH) I can also ping itself:
Code:
ping $(uname -n)
PING srv-vir01.tuxdomain (192.168.120.40) 56(84) bytes of data.
64 bytes from srv-vir01.tuxdomain (192.168.120.40): icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from srv-vir01.tuxdomain (192.168.120.40): icmp_seq=2 ttl=64 time=0.035 ms
64 bytes from srv-vir01.tuxdomain (192.168.120.40): icmp_seq=3 ttl=64 time=0.034 ms
64 bytes from srv-vir01.tuxdomain (192.168.120.40): icmp_seq=4 ttl=64 time=0.034 ms
64 bytes from srv-vir01.tuxdomain (192.168.120.40): icmp_seq=5 ttl=64 time=0.034 ms
64 bytes from srv-vir01.tuxdomain (192.168.120.40): icmp_seq=6 ttl=64 time=0.034 ms

However in the WebUI I see that all elements now have a grey question mark and tooltip saying "Status unknown". I have restarted the network service (systemctl restart networking) and even rebooted the node...

1736035895431.png

syslog shows a LOT of:
Code:
Jan 04 18:39:53 srv-vir01.tuxdomain pveproxy[3154]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2000.

Jan 04 18:43:05 srv-vir01.tuxdomain pmxcfs[3287]: [main] crit: Unable to get local IP address

Something has not followed up after the IP change.... How can I debug this?

EDIT: Additional data
/etc/resolv.conf
Code:
search tuxdomain

nameserver 192.168.120.1

/etc/network/interfaces
Code:
auto lo
iface lo inet loopback
iface enp2s0 inet manual

auto vmbr0

iface vmbr0 inet static
        address 192.168.120.40/24
        gateway 192.168.120.1
        bridge-ports enp2s0
        bridge-stp off
        bridge-fd 0

iface enp3s0 inet manual

/etc/hosts
Code:
127.0.0.1 localhost.localdomain localhost
192.168.120.40 srv-vir01.tuxdomain

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

pveversion -v
Code:
proxmox-ve: 7.4-1 (running kernel: 5.15.158-2-pve)
pve-manager: 7.4-19 (running version: 7.4-19/f98bf8d4)
pve-kernel-5.15: 7.4-15
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.15.158-1-pve: 5.15.158-1
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.3
libpve-apiclient-perl: 3.2-2
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.3.0
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-4
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.7-1
proxmox-backup-file-restore: 2.4.7-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.4
pve-cluster: 7.3-3
pve-container: 4.4-7
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+3
pve-firewall: 4.3-5
pve-firmware: 3.6-6
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.10-1
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-6
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.15-pve1
 
Last edited:
OK this morning I logged in to the webUI and its back to normal.

I consider this not resolved. What may have happened and why?