"RTNETLINK answers: File exists" after kernel update

aeris · Dec 4, 2019

Hi,

I am on stretch and Proxmox 5.4-13 at OVH

After a kernel update and after reboot, I have this error :

Bash:

root@opale:~# /etc/init.d/networking restart
[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code.
See "systemctl status networking.service" and "journalctl -xe" for details.
failed!
root@opale:~# systemctl status networking.service
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-12-04 09:45:08 CET; 18min ago
     Docs: man:interfaces(5)
  Process: 2720 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 2705 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)
Main PID: 2720 (code=exited, status=1/FAILURE)
      CPU: 493ms

Dec 04 09:45:07 opale systemd[1]: Starting Raise network interfaces...
Dec 04 09:45:07 opale ifup[2720]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Dec 04 09:45:08 opale ifup[2720]: RTNETLINK answers: File exists
Dec 04 09:45:08 opale ifup[2720]: ifup: failed to bring up vmbr0
Dec 04 09:45:08 opale systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Dec 04 09:45:08 opale systemd[1]: Failed to start Raise network interfaces.
Dec 04 09:45:08 opale systemd[1]: networking.service: Unit entered failed state.
Dec 04 09:45:08 opale systemd[1]: networking.service: Failed with result 'exit-code'.

Config :

Bash:

root@opale:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
        address  176.xxx.xxx.xxx
        netmask  24
        gateway  176.xxx.xxx.254
        bridge-ports eth0
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE

auto vmbr1
iface vmbr1 inet static
        address  192.168.0.1
        netmask  24
        bridge-ports none
        bridge-stp off
        bridge-fd 0

        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 22 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 22 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 25 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 25 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 587 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 587 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 110 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 110 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 143 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 145 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 995 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 995 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 993 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 993 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 123 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 123 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 3128 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 3128 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 5222 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 5222 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 5269 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 5269 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 64738 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 64738 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p udp --dport 64738 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p udp --dport 64738 -j DNAT --to 192.168.0.100
        post-up iptables -t nat -A PREROUTING -i vmbr0 -p udp --dport 4242 -j DNAT --to 192.168.0.100
        post-down iptables -t nat -D PREROUTING -i vmbr0 -p udp --dport 4242 -j DNAT --to 192.168.0.100

When i do :

Bash:

root@opale:~# ifup --ignore-errors vmbr0

Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
RTNETLINK answers: File exists
RTNETLINK answers: File exists

It work temporary.

Do you have an idea, please ?

t.lamprecht · Dec 4, 2019

What's your current network state: ip addr

t.lamprecht · Dec 4, 2019

aeris said:
It work temporary.

For this boot or for a shorter period?

aeris · Dec 4, 2019

t.lamprecht said:
For this boot or for a shorter period?

For this boot.

After a new boot :

Bash:

root@opale:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 00:22:4d:7a:4d:5c brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:22:4d:7a:4d:5c brd ff:ff:ff:ff:ff:ff
    inet 176.31.121.42/24 brd 176.31.121.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 2001:41d0:8:402a::1/128 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::222:4dff:fe7a:4d5c/64 scope link
       valid_lft forever preferred_lft forever
4: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether a6:37:14:d0:56:d9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.1/24 brd 192.168.0.255 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 fe80::a437:14ff:fed0:56d9/64 scope link
       valid_lft forever preferred_lft forever

After restarting networking :

Code:

root@opale:~# /etc/init.d/networking restart
[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code.
See "systemctl status networking.service" and "journalctl -xe" for details.
 failed!
root@opale:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 00:22:4d:7a:4d:5c brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:22:4d:7a:4d:5c brd ff:ff:ff:ff:ff:ff
    inet 176.31.121.42/24 brd 176.31.121.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 2001:41d0:8:402a::1/128 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::222:4dff:fe7a:4d5c/64 scope link
       valid_lft forever preferred_lft forever
4: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 56:c0:70:4f:80:ed brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.1/24 brd 192.168.0.255 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 fe80::a437:14ff:fed0:56d9/64 scope link
       valid_lft forever preferred_lft forever
6: veth100i0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether fe:3e:7a:fe:f4:27 brd ff:ff:ff:ff:ff:ff link-netnsid 0
7: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 86:bf:0a:62:19:89 brd ff:ff:ff:ff:ff:ff
8: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether 56:c0:70:4f:80:ed brd ff:ff:ff:ff:ff:ff
9: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether 86:bf:0a:62:19:89 brd ff:ff:ff:ff:ff:ff

Hum...
But I dont know what are this

Search

Search

"RTNETLINK answers: File exists" after kernel update

aeris

Active Member

t.lamprecht

Proxmox Staff Member

t.lamprecht

Proxmox Staff Member

aeris

Active Member