[SOLVED] pve 4.1 node network config not showing in webgui

J

jester

Renowned Member
Proxmox Subscriber
Aug 17, 2014
23
2
68
I've got something weird again :(

Noticed yesterday that my servers's network settings are not showing (see attached screenshot). And in the pending changes section there is a: 'Error: failed to open socket (500)'. Rebooted the server, still the same. All vm's are working fine though.

Been searching my ass off, but i'm at a loss here.
Anyone with a wild or educated guess how to solve this?

pve4.1_no_node_network_config.jpg
 
Could you show us the output of the following command please? ip addr show
EDIT:
Also, is there anything unusual about your setup? Is it a custom kernel?
What package versions are you using (pveversion -v)?
 
Last edited:
Hi Wolfgang,
Nope, it's a standard kernel. The requested output:
Code: 
root@pmx01:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr1 state DOWN group default qlen 1000
    link/ether 00:10:18:4f:8b:a4 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:10:18:4f:8b:a6 brd ff:ff:ff:ff:ff:ff
4: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether b8:ca:3a:ba:35:92 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether b8:ca:3a:ba:35:92 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.250/24 brd 10.0.1.255 scope global vmbr0
       valid_lft forever preferred_lft forever
6: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 00:10:18:4f:8b:a4 brd ff:ff:ff:ff:ff:ff
7: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/ether e2:cb:cb:b1:ef:44 brd ff:ff:ff:ff:ff:ff
8: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 500
    link/ether 0a:af:2b:26:d5:f0 brd ff:ff:ff:ff:ff:ff
9: tap103i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 500
    link/ether 46:2a:90:fe:cb:7d brd ff:ff:ff:ff:ff:ff
14: tap105i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 500
    link/ether 5e:39:4e:fb:0e:aa brd ff:ff:ff:ff:ff:ff
16: veth104i0@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether fe:3c:22:79:03:41 brd ff:ff:ff:ff:ff:ff link-netnsid 1
18: veth101i0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether fe:cc:4b:7f:72:67 brd ff:ff:ff:ff:ff:ff link-netnsid 0
 
Do you happen to be using a kernel boot option to disable ipv6? (There's currently a patch pending to fix a regression there (missing ipv4 fallback for a socket...))
 
Will be fixed with the next updates, too. Although I can't quite imagine why anyone would still be using IPv4 and not IPv6 ;)
 
  • Like
Reactions: ordinatous
You must log in or register to reply here.
Top Bottom