Failed to start Raise network interfaces.

J

jemico

Member
Nov 2, 2019
7
0
6
Hi,

Networking seems all fine (ping google, ssh connect) but host totally disconnect from time to time (quite every 2 days ... :( )and we have to reboot it, and networking.service fail to start ....

I'm running 4.15.18-27-pve with this kind of network config :

root@bks:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether 0c:c4:7a:c3:53:a6 brd ff:ff:ff:ff:ff:ff
3: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
link/ether 0c:c4:7a:c3:53:a7 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 0c:c4:7a:c3:53:a6 brd ff:ff:ff:ff:ff:ff
5: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 0c:c4:7a:c3:53:a7 brd ff:ff:ff:ff:ff:ff
6: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 96:ed:50:b4:f2:c4 brd ff:ff:ff:ff:ff:ff

root@bks:~# ip address
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: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 0c:c4:7a:c3:53:a6 brd ff:ff:ff:ff:ff:ff
3: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
link/ether 0c:c4:7a:c3:53:a7 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0c:c4:7a:c3:53:a6 brd ff:ff:ff:ff:ff:ff
inet 111.222.111.222/24 brd 111.222.333.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 2001:2222:3333:4444::/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::ec4:7aff:fec3:53a6/64 scope link
valid_lft forever preferred_lft forever
5: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0c:c4:7a:c3:53:a7 brd ff:ff:ff:ff:ff:ff
inet 10.1.0.3/24 brd 10.1.0.255 scope global vmbr1
valid_lft forever preferred_lft forever
inet6 fe80::ec4:7aff:fec3:53a7/64 scope link
valid_lft forever preferred_lft forever
6: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 96:ed:50:b4:f2:c4 brd ff:ff:ff:ff:ff:ff
inet 10.2.0.254/16 brd 10.2.255.255 scope global vmbr2
valid_lft forever preferred_lft forever
inet6 fe80::94ed:50ff:feb4:f2c4/64 scope link
valid_lft forever preferred_lft forever

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

iface eno3 inet manual

iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
address 111.222.111.222
netmask 24
gateway 111.222.111.254
bridge-ports eno3
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet static
address 10.1.0.3
netmask 24
bridge-ports eno4
bridge-stp off
bridge-fd 0

auto vmbr2
iface vmbr2 inet static
address 10.2.0.254
netmask 16
bridge-ports none
bridge-stp off
bridge-fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '10.2.0.0/16' -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '10.2.0.0/16' -o vmbr0 -j MASQUERADE


but networking.serivces is like that :

root@bks:~# 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 Fri 2020-04-17 15:20:33 CEST; 27min ago
Docs: man:interfaces(5)
Process: 1907 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 1740 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
Main PID: 1907 (code=exited, status=1/FAILURE)
CPU: 427ms

avril 17 15:20:31 bks systemd[1]: Starting Raise network interfaces...
avril 17 15:20:32 bks ifup[1907]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
avril 17 15:20:32 bks ifup[1907]: RTNETLINK answers: File exists
avril 17 15:20:32 bks ifup[1907]: ifup: failed to bring up vmbr0
avril 17 15:20:33 bks ifup[1907]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
avril 17 15:20:33 bks ifup[1907]: Waiting for vmbr2 to get ready (MAXWAIT is 2 seconds).
avril 17 15:20:33 bks systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
avril 17 15:20:33 bks systemd[1]: Failed to start Raise network interfaces.
avril 17 15:20:34 bks systemd[1]: networking.service: Unit entered failed state.
avril 17 15:20:34 bks systemd[1]: networking.service: Failed with result 'exit-code'.


I rebooted without vmbr2 and its masquerading without success ....
would you have any idea of what could go wrong ?


Jean-Michel
 
Hi,

are there hints in the syslog or the journal?
 
Hello,

Sorry for the delay : I didn't find anything for now.
Multiple reboots happens on this machine without any log, and now I've got no more network with the same config => as is, I've open an incident to the provider (OVH) because at first sight, I've got the impression of a hardware problem ....
I tell you all when I've got news.

Thanks !!!
 
Hello,

Today I had no more network on the serveur, and the provider did an down/up on the NIC, with success.
I wished that it solved my problem .... but no : networking.service always failed with same error.

Here is the result of journalctl -p err :

avril 22 20:54:27 bks kernel: Couldn't get size: 0x800000000000000e
avril 22 20:54:27 bks kernel: MODSIGN: Couldn't get UEFI db list
avril 22 20:54:27 bks kernel: Couldn't get size: 0x800000000000000e
avril 22 20:54:27 bks kernel: Couldn't get size: 0x800000000000000e
avril 22 20:54:27 bks kernel: pstore: decompression failed: -5
avril 22 20:54:27 bks kernel: pstore: decompression failed: -5
avril 22 20:54:36 bks systemd[1]: Failed to start Raise network interfaces.

Does it helps in any way ? Do you think it would be interresting to push another log ?
I don't arrive to find what I'm missing .... :-/

Jean-Michel
 
jemico said:
Does it helps in any way ?
Click to expand...
Not really it says only it can't raise the network but not where it fails.
Please also check the journal

Code: 
journalctl -u networking.service

What nic model do you got in this server?
 
Hello Wolfgang,

root@bks:~# journalctl -u networking.service
-- Logs begin at Wed 2020-04-22 22:34:13 CEST, end at Thu 2020-04-23 06:46:00 CEST. --
avril 22 22:34:19 bks systemd[1]: Starting Raise network interfaces...
avril 22 22:34:20 bks ifup[2064]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
avril 22 22:34:21 bks ifup[2064]: RTNETLINK answers: File exists
avril 22 22:34:21 bks ifup[2064]: ifup: failed to bring up vmbr0
avril 22 22:34:21 bks ifup[2064]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
avril 22 22:34:21 bks ifup[2064]: Waiting for vmbr2 to get ready (MAXWAIT is 2 seconds).
avril 22 22:34:22 bks systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
avril 22 22:34:22 bks systemd[1]: Failed to start Raise network interfaces.
avril 22 22:34:22 bks systemd[1]: networking.service: Unit entered failed state.
avril 22 22:34:22 bks systemd[1]: networking.service: Failed with result 'exit-code'.

root@bks:/etc# lshw -class network
*-network:0
description: Ethernet interface
produit: Ethernet Connection X552/X557-AT 10GBASE-T
fabriquant: Intel Corporation
identifiant matériel: 0
information bus: pci@0000:03:00.0
nom logique: eno3
version: 00
numéro de série: 0c:c4:7a:c3:53:a6
taille: 10Gbit/s
capacité: 10Gbit/s
bits: 64 bits
horloge: 33MHz
fonctionnalités: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 1000bt-fd 10000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ixgbe driverversion=5.1.0-k duplex=full firmware=0x800003e7 latency=0 link=yes multicast=yes port=twisted pair speed=10Gbit/s
ressources: mémoireE/S:383f0-383ef mémoireE/S:383f0-383ef irq:16 mémoire:383fffc00000-383fffdfffff mémoire:383fffe04000-383fffe07fff mémoire:fb180000-fb1fffff mémoire:fb500000-fb5fffff mémoire:fb400000-fb4fffff
*-network:1
description: Ethernet interface
produit: Ethernet Connection X552/X557-AT 10GBASE-T
fabriquant: Intel Corporation
identifiant matériel: 0.1
information bus: pci@0000:03:00.1
nom logique: eno4
version: 00
numéro de série: 0c:c4:7a:c3:53:a7
taille: 10Gbit/s
capacité: 10Gbit/s
bits: 64 bits
horloge: 33MHz
fonctionnalités: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 1000bt-fd 10000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ixgbe driverversion=5.1.0-k duplex=full firmware=0x800003e7 latency=0 link=yes multicast=yes port=twisted pair speed=10Gbit/s
ressources: mémoireE/S:383f0-383ef mémoireE/S:383f0-383ef irq:17 mémoire:383fffa00000-383fffbfffff mémoire:383fffe00000-383fffe03fff mémoire:fb100000-fb17ffff mémoire:fb300000-fb3fffff mémoire:fb200000-fb2fffff
*-network:0
description: Ethernet interface
identifiant matériel: 3
nom logique: vmbr0
numéro de série: 0c:c4:7a:c3:53:a6
fonctionnalités: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=111.222.111.222 link=yes multicast=yes
*-network:1
description: Ethernet interface
identifiant matériel: 4
nom logique: vmbr2
numéro de série: e2:46:df:a0:b7:0c
fonctionnalités: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=10.2.0.254 link=yes multicast=yes
*-network:2
description: Ethernet interface
identifiant matériel: 5
nom logique: vmbr1
numéro de série: 0c:c4:7a:c3:53:a7
fonctionnalités: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=10.1.0.3 link=yes multicast=yes

Regards,
Jean-Michel
 
Hello,

Since last time, we started server with another OS (rescue mode) and ..... had the very same kind of crash !
It seems to be a hardware problem and not a proxmox config one.

Regards,
Jean-Michel
 
Hi all,

After solving the hardware crash (motherboard changed), I always had the same network behavior.
Finally, I found a solution :

Explanation :
The server is OVH and their Proxmox 5 ZFS image start both networking.service and systemd-networkd.service.
The default OVH configuration is mostly done in systemd-networkd.service (/etc/systemd/network/) and may conflict with (/etc/network/interface)....
It doesn't seem to be always problematic (not on all servers). I didn't investigated much more for now (starting order ? other ?) ...

Solution (for me !) :
  1. configure /etc/network/interface fully & correctly
  2. systemctl stop systemd-networkd.service
  3. systemctl disable systemd-networkd.service
  4. systemctl restart networking.service
Hope it can helps someone,

Regards,
Jean-Michel
 
You must log in or register to reply here.
Top Bottom