Failed to start: Raise network interfaces [SOLVED]

LESHIY.OD · Aug 25, 2019

Hi

The network went missing this morning. Nothing was done the day before.

It is very important to start the server by Monday.

aaron · Aug 26, 2019

Did you reboot with kexec? I found this bug where the intel_ish_ipc driver fails on kexec with the errors your screenshot shows and needs a complete reboot [0].

[0]: https://bugzilla.kernel.org/show_bug.cgi?id=198543

LESHIY.OD · Aug 26, 2019

aaron said:
[0]: https://bugzilla.kernel.org/show_bug.cgi?id=198543

I've seen this message, but I didn't know exactly what to do. I tried to load the old kernel via grub, but that didn't help.
I'm not very good at Linux, could you tell me exactly what to do to fix this bug?
At the moment I have reinstalled Promox 5.4 ➜ 6.0, the network is working, but the error still appears.

Aug 26 03:27:37 SERVER kernel: intel_ish_ipc 0000:00:13.0: [ishtp-ish]: Timed out waiting for FW-initiated reset
Aug 26 03:27:37 SERVER kernel: intel_ish_ipc 0000:00:13.0: ISH: hw start failed.

Thank you for your quick response.

aaron · Aug 27, 2019

I did a bit more research as I haven't seen the `intel_ish_ipc` before. It's the integrated sensor hub. Maybe there are new BIOS and firmware versions available for you hardware.

But that has nothing to do with the network as far as I understand. Whatever caused the network problems seems to be gone now with the reinstall.

LESHIY.OD · Aug 27, 2019

aaron said:
I did a bit more research as I haven't seen the `intel_ish_ipc` before. It's the integrated sensor hub.

I had a panic and I thought the whole PCI line was down.

aaron said:
Maybe there are new BIOS and firmware versions available for you hardware.

You're right, that's the first thing I did, updated the BIOS and IPMI.

aaron said:
But that has nothing to do with the network as far as I understand. Whatever caused the network problems seems to be gone now with the reinstall.

Yesterday I had such suspicions that it had nothing to do with the network.

I have the same thing now, but it works. Before reinstalling ifconfig, only one interface is shown - lo. The system hasn't seen any network interfaces.

Tonight — ISH: hw start failed + Failed to start Raise network interfaces

еееееееееее.avi_snapshot_00.53_[2019.08.27_12.11.24].jpg

Code:

root@SERVER:~# 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 Tue 2019-08-27 01:35:39 EEST; 10h ago
     Docs: man:interfaces(5)
  Process: 668 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
 Main PID: 668 (code=exited, status=1/FAILURE)

авг 27 01:35:38 SERVER ifup[668]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
авг 27 01:35:39 SERVER ifup[668]: RTNETLINK answers: File exists
авг 27 01:35:39 SERVER ifup[668]: ifup: failed to bring up vmbr1
авг 27 01:35:39 SERVER ifup[668]: Waiting for vmbr2 to get ready (MAXWAIT is 2 seconds).
авг 27 01:35:39 SERVER ifup[668]: Waiting for vmbr110 to get ready (MAXWAIT is 2 seconds).
авг 27 01:35:39 SERVER ifup[668]: Waiting for vmbr105 to get ready (MAXWAIT is 2 seconds).
авг 27 01:35:39 SERVER ifup[668]: Waiting for vmbr150 to get ready (MAXWAIT is 2 seconds).
авг 27 01:35:39 SERVER systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
авг 27 01:35:39 SERVER systemd[1]: networking.service: Failed with result 'exit-code'.
авг 27 01:35:39 SERVER systemd[1]: Failed to start Raise network interfaces.

aaron · Aug 27, 2019

What is the content of you `/etc/network/interfaces` file?

Code:

cat /etc/network/interfaces

What is the output of

Code:

ip a

?

If you have public IP addresses redact them

LESHIY.OD · Aug 27, 2019

It's now installed — Proxmox VE 6.0. On Sunday, when the failure was set — 5.4.
vmbr0 — WAN port — MikroTik-CHR.

/etc/network/interfaces

Code:

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug eno1
allow-hotplug eno2
allow-hotplug enp2s0

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto enp2s0
iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet dhcp
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address  10.1.3.101
        netmask  255.255.255.0
        gateway  10.1.3.1
        bridge-ports eno2
        bridge-stp off
        bridge-fd 0

auto vmbr2
iface vmbr2 inet manual
        bridge-ports enp2s0
        bridge-stp off
        bridge-fd 0

auto vmbr110
iface vmbr110 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr105
iface vmbr105 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr150
iface vmbr150 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0

ip a

Code:

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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr2 state DOWN group default qlen 1000
    link/ether 74:da:38:d8:98:fc brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:de brd ff:ff:ff:ff:ff:ff
4: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:df brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:de brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.101/24 brd 10.1.1.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::ae1f:6bff:fe91:ede/64 scope link
       valid_lft forever preferred_lft forever
6: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:df brd ff:ff:ff:ff:ff:ff
    inet 10.1.3.101/24 brd 10.1.3.255 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 fe80::ae1f:6bff:fe91:edf/64 scope link
       valid_lft forever preferred_lft forever
7: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 74:da:38:d8:98:fc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::76da:38ff:fed8:98fc/64 scope link
       valid_lft forever preferred_lft forever
8: vmbr110: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 56:19:63:6e:92:f5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::888:80ff:fe90:1d48/64 scope link
       valid_lft forever preferred_lft forever
9: vmbr105: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:41:8d:12:f1:cc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::10ff:76ff:fef2:d381/64 scope link
       valid_lft forever preferred_lft forever
10: vmbr150: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 42:bd:54:df:d9:5c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d8ec:e1ff:fe43:9057/64 scope link
       valid_lft forever preferred_lft forever
11: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether be:ef:4e:38:39:8c brd ff:ff:ff:ff:ff:ff
12: tap100i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether d2:8d:6a:d4:0b:e5 brd ff:ff:ff:ff:ff:ff
13: tap100i2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr2 state UNKNOWN group default qlen 1000
    link/ether 62:4f:27:58:39:14 brd ff:ff:ff:ff:ff:ff
14: tap100i3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr105 state UNKNOWN group default qlen 1000
    link/ether 1e:41:8d:12:f1:cc brd ff:ff:ff:ff:ff:ff
15: tap100i4: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr110 state UNKNOWN group default qlen 1000
    link/ether 56:19:63:6e:92:f5 brd ff:ff:ff:ff:ff:ff
16: tap100i5: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr150 state UNKNOWN group default qlen 1000
    link/ether 42:bd:54:df:d9:5c brd ff:ff:ff:ff:ff:ff
19: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr110 state UNKNOWN group default qlen 1000
    link/ether 8a:8a:2a:58:01:f3 brd ff:ff:ff:ff:ff:ff
20: tap105i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr105 state UNKNOWN group default qlen 1000
    link/ether 5e:7e:17:7c:2b:1a brd ff:ff:ff:ff:ff:ff
21: tap105i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether fe:15:ec:57:81:98 brd ff:ff:ff:ff:ff:ff

aaron · Aug 28, 2019

Okay, the config doesn't look wrong.

So if you start the server, now installed with PVE 6.0, you still get the error "Failed to start: Raise network interfaces"?

If so can you show the full logs of the networking service? The output in the `systemctl status networking.service` is a bit short.

Code:

journalctl -u networking.service

LESHIY.OD · Aug 28, 2019

aaron said:
So if you start the server, now installed with PVE 6.0, you still get the error "Failed to start: Raise network interfaces"?

Yes.

aaron said:
If so can you show the full logs of the networking service? The output in the `systemctl status networking.service` is a bit short.

Code:

авг 28 23:01:06 SERVER systemd[1]: Starting Raise network interfaces...
авг 28 23:01:06 SERVER ifup[664]: ifup: waiting for lock on /run/network/ifstate.eno1
авг 28 23:01:07 SERVER ifup[664]: ifup: waiting for lock on /run/network/ifstate.eno2
авг 28 23:01:07 SERVER ifup[664]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
авг 28 23:01:07 SERVER dhclient[804]: Internet Systems Consortium DHCP Client 4.4.1
авг 28 23:01:07 SERVER ifup[664]: Internet Systems Consortium DHCP Client 4.4.1
авг 28 23:01:07 SERVER ifup[664]: Copyright 2004-2018 Internet Systems Consortium.
авг 28 23:01:07 SERVER ifup[664]: All rights reserved.
авг 28 23:01:07 SERVER ifup[664]: For info, please visit https://www.isc.org/software/dhcp/
авг 28 23:01:07 SERVER dhclient[804]: Copyright 2004-2018 Internet Systems Consortium.
авг 28 23:01:07 SERVER dhclient[804]: All rights reserved.
авг 28 23:01:07 SERVER dhclient[804]: For info, please visit https://www.isc.org/software/dhcp/
авг 28 23:01:07 SERVER dhclient[804]:
авг 28 23:01:07 SERVER dhclient[804]: Listening on LPF/vmbr0/ac:1f:6b:91:0e:de
авг 28 23:01:07 SERVER ifup[664]: Listening on LPF/vmbr0/ac:1f:6b:91:0e:de
авг 28 23:01:07 SERVER ifup[664]: Sending on   LPF/vmbr0/ac:1f:6b:91:0e:de
авг 28 23:01:07 SERVER ifup[664]: Sending on   Socket/fallback
авг 28 23:01:07 SERVER ifup[664]: DHCPREQUEST for 10.1.1.101 on vmbr0 to 255.255.255.255 port 67
авг 28 23:01:07 SERVER dhclient[804]: Sending on   LPF/vmbr0/ac:1f:6b:91:0e:de
авг 28 23:01:07 SERVER dhclient[804]: Sending on   Socket/fallback
авг 28 23:01:07 SERVER dhclient[804]: DHCPREQUEST for 10.1.1.101 on vmbr0 to 255.255.255.255 port 67
авг 28 23:01:14 SERVER dhclient[804]: DHCPREQUEST for 10.1.1.101 on vmbr0 to 255.255.255.255 port 67
авг 28 23:01:14 SERVER ifup[664]: DHCPREQUEST for 10.1.1.101 on vmbr0 to 255.255.255.255 port 67
авг 28 23:01:14 SERVER dhclient[804]: DHCPACK of 10.1.1.101 from 10.1.1.1
авг 28 23:01:14 SERVER ifup[664]: DHCPACK of 10.1.1.101 from 10.1.1.1
авг 28 23:01:14 SERVER dhclient[804]: Timeout too large reducing to: 2147483646 (TIME_MAX - 1)
авг 28 23:01:14 SERVER ifup[664]: Timeout too large reducing to: 2147483646 (TIME_MAX - 1)
авг 28 23:01:14 SERVER ifup[664]: bound to 10.1.1.101 -- renewal in 2147483648 seconds.
авг 28 23:01:14 SERVER dhclient[804]: bound to 10.1.1.101 -- renewal in 2147483648 seconds.
авг 28 23:01:14 SERVER ifup[664]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
авг 28 23:01:14 SERVER ifup[664]: RTNETLINK answers: File exists
авг 28 23:01:14 SERVER ifup[664]: ifup: failed to bring up vmbr1
авг 28 23:01:14 SERVER ifup[664]: Waiting for vmbr2 to get ready (MAXWAIT is 2 seconds).
авг 28 23:01:14 SERVER ifup[664]: Waiting for vmbr110 to get ready (MAXWAIT is 2 seconds).
авг 28 23:01:14 SERVER ifup[664]: Waiting for vmbr105 to get ready (MAXWAIT is 2 seconds).
авг 28 23:01:14 SERVER ifup[664]: Waiting for vmbr150 to get ready (MAXWAIT is 2 seconds).
авг 28 23:01:15 SERVER systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
авг 28 23:01:15 SERVER systemd[1]: networking.service: Failed with result 'exit-code'.
авг 28 23:01:15 SERVER systemd[1]: Failed to start Raise network interfaces.

Highlighted in red — авг 28 23:01:14 SERVER dhclient[804]: Timeout too large reducing to: 2147483646 (TIME_MAX - 1)
Highlighted in red — авг 28 23:01:15 SERVER systemd[1]: Failed to start Raise network interfaces.

10.1.1.1 — router openwrt (internet).

Code:

config host
    option dns '1'
    option ip '10.1.1.101'
    option leasetime 'infinite'
    option name 'SERVER-LAN1'
    option mac 'AC:1F:6B:91:0E:DE'

10.1.1.101 — server Proxmox (vmbr0 — dhcp).

LESHIY.OD · Aug 28, 2019

If you set a static IP, the log will be as follows:

Code:

auto vmbr0
iface vmbr0 inet static
    address  10.1.1.101
    netmask  255.255.255.0
    gateway  10.1.1.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
#WAN

Code:

root@SERVER:~# journalctl -u networking.service
-- Logs begin at Wed 2019-08-28 23:37:00 EEST, end at Wed 2019-08-28 23:37:14 EEST. --
авг 28 23:37:03 SERVER systemd[1]: Starting Raise network interfaces...
авг 28 23:37:03 SERVER ifup[679]: ifup: waiting for lock on /run/network/ifstate.eno1
авг 28 23:37:03 SERVER ifup[679]: ifup: waiting for lock on /run/network/ifstate.enp2s0
авг 28 23:37:04 SERVER ifup[679]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
авг 28 23:37:04 SERVER ifup[679]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
авг 28 23:37:04 SERVER ifup[679]: RTNETLINK answers: File exists
авг 28 23:37:04 SERVER ifup[679]: ifup: failed to bring up vmbr1
авг 28 23:37:04 SERVER ifup[679]: Waiting for vmbr2 to get ready (MAXWAIT is 2 seconds).
авг 28 23:37:04 SERVER ifup[679]: Waiting for vmbr110 to get ready (MAXWAIT is 2 seconds).
авг 28 23:37:04 SERVER ifup[679]: Waiting for vmbr105 to get ready (MAXWAIT is 2 seconds).
авг 28 23:37:04 SERVER ifup[679]: Waiting for vmbr150 to get ready (MAXWAIT is 2 seconds).
авг 28 23:37:04 SERVER systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
авг 28 23:37:04 SERVER systemd[1]: networking.service: Failed with result 'exit-code'.
авг 28 23:37:04 SERVER systemd[1]: Failed to start Raise network interfaces.

Highlighted in red — авг 28 23:37:04 SERVER systemd[1]: Failed to start Raise network interfaces.

aaron · Aug 29, 2019

Ah, it took me a while to realize this but what is biting you is most likely the gateway for vmbr1.
vmbr0 already gets a gateway via dhcp and there can only be one default gateway.

Remove the `gateway` line from the vmbr1 config.

If you want more gateways you need to set it in a `post-up` line and specify for which routes it should be used instead of the default.

LESHIY.OD · Aug 29, 2019

Yes, yes, yes!!!

It's so simple and obvious, you can't see it right away.

As for the error intel_ish_ipc ISH: hw start failed, I think I will do the same as I did with error driver pcspkr - nano /etc/modprobe.d/pve-blacklist.conf ➜ blacklist intel_ish_ipc ISH update — it didn't work out

Thank you very much for helping me to understand. You are a genius!

MrValvin · Jan 24, 2021

I also get the intel_ish_ipc error on all my servers, all with Intel C230 chipset, all SuperMicro X11 boards.

Device:

00:13.0 Non-VGA unclassified device: Intel Corporation 100 Series C230 Series Chipset Family Integrated Sensor Hub (rev 31)

I wonder if the driver just doesn't work with C230, or is it related to SuperMicro? Gets the error on both Debian Buster (kernel 5.8.10-1) and openSUSE 15.2 (kernel 5.3.18).
Don't see any issues though, seems to run fine. But hard to say if I'm missing some monitoring/sensor/alarm functionality.

MrValvin · Jan 27, 2021

Rumor has it it's a kernel bug:
https://www.supermicro.com/support/faqs/faq.cfm?faq=31505

José Claudio · Feb 16, 2021

Boa tarde amigos, preciso instalar o proxmox em uma máquina e depois levar o disco para um servidor que não tem dvd nem boot por USB.

Após instalar ele pega o apelido da placa no servidor 1 como epn3s01 e funciona normal.

No servidor de produção quando coloco o disco ele pela o apelido como eno1

Então eu acesso / etc / rede / interface e altero

auto vmbr0
iface vmbr0 inet static
endereço 10.1.1.101
máscara de rede 255.255.255.0
gateway 10.1.1.1
bridge-ports eno1
ponte-stp off
bridge-fd 0
#WAN

Após reiniciar o proxmox já não há carregamento eu tomo ou erro Falha ao iniciar: aumentar interfaces de rede

Quando o servir sobe ao ver o IP addr não tem IP e nem o vmbr01 apenas eno1 e eno2 sem IP

Alguém poderia me dar uma luz agradeço desde já

Search

Search

Failed to start: Raise network interfaces [SOLVED]

LESHIY.OD

Active Member

aaron

Proxmox Staff Member

LESHIY.OD

Active Member

aaron

Proxmox Staff Member

LESHIY.OD

Active Member

aaron

Proxmox Staff Member

LESHIY.OD

Active Member

aaron

Proxmox Staff Member

LESHIY.OD

Active Member

LESHIY.OD

Active Member

aaron

Proxmox Staff Member

LESHIY.OD

Active Member

MrValvin

Member

MrValvin

Member

José Claudio

Active Member