Failed to start raise network interfaces astra linux

Не удалось запустить Поднять сетевые интерфейсы после обновления до 16.04

Я только что обновил виртуальный сервер 14.04 до 16.04. После перезагрузки виртуальной машины я вижу следующую ошибку:

После входа в систему я могу выполнить указанную команду и получить следующий вывод (изображение, поскольку я не могу подключиться):

Конфигурация в /etc/network/interfaces выглядит хорошо — показывает настроенный вручную eth0 (здесь не используется dhcp)

Что меня удивляет, так это ifconfig -a списки

Где бы я ожидал

Попытка поднять устройство eth0 через

Само устройство виртуальной проводной сети по-прежнему настроено в самой виртуальной машине, как и прежде.

ip link также показывает lo и ens160 — где ens160 настроен mac-адрес в vmware для одного настроенного виртуального сетевого устройства.

ОБНОВИТЬ

Я могу решить эту проблему, если я изменю все ссылки с eth0 /etc/network/interfaces на ens160.

НО — это неправильно для меня по нескольким причинам:

1. Я хотел бы понять эту проблему
2. Я хотел бы придерживаться eth0 вместо ens160

Поэтому, пожалуйста, кто-то может объяснить это изменение, которое не произошло с несколькими другими машинами 14.04 на том же сервере, который я также обновил до 16.04.

причина

Проблема была вызвана Predictable-Network-Interface-Names из systemd / udev.

Возможное решение

Согласно этому источнику вы можете:

• Вы отключаете назначение фиксированных имен, чтобы непредсказуемые имена ядра использовались снова. Для этого просто замаскируйте файл правил udev для политики по умолчанию: ln -s / dev / null /etc/udev/rules.d/80-net-setup-link.rules
• Вы создаете свою собственную схему именования вручную, например, называя свои интерфейсы «internet0», «dmz0» или «lan0». Для этого создайте свои собственные файлы .link в / etc / systemd / network /, которые выбирают явное имя или лучшую схему именования для одного, нескольких или всех ваших интерфейсов. Смотрите systemd.link (5) для получения дополнительной информации.
• Вы передаете net.ifnames = 0 в командной строке ядра

Прикладные решения

Я сделал создать новый файл 10-rename-network.rules в /etc/udev/rules.d/ и добавил следующее содержание к нему:

• eth0 = желаемое имя сетевого интерфейса, используется в /etc/network/interfaces
• ff:ff:ff:ff:ff:ff = аппаратный mac-адрес сетевого устройства

Я бы порекомендовал перезагрузить компьютер после его завершения, чтобы убедиться, что изменения не изменились

Источник

Failed to start Raise network interfaces

Sergio Rodriguez

New Member

I recently installed Debian and I’m getting the following message at startup:

I run that command and I got the following message:

Well-Known Member

wizardfromoz

Administrator

I have some input for this Thread

(Wizard appears in a puff of smoke)

. but I want to run a couple of experiments first, and then put together some information that is cohesive and factual. Might take me a couple of days.

Can I ask of both of you whether your wifi is actually working (ie the error is non-fatal) or not, on your Debians?

Chris Turner
wizardfromoz

Well-Known Member

Condobloke

Well-Known Member

Condobloke . Outback Australian :: LINUX IS THE ANSWER. LINUX MINT used EXCLUSIVELY here.

I like long walks, especially when they are taken by people that annoy me.

Live simply. Love generously. Care deeply. Speak kindly …. Especially in C19 times.

It has been said that time heals all wounds. I don’t agree. The wounds remain. Time — the mind, protecting its sanity — covers them with some scar tissue and the pain lessens, but it is never gone. Rose Kennedy.

Источник

Thread: Failed to start Raise network interfaces.

Thread Tools

Display

Failed to start Raise network interfaces.

Doing a fresh Server Install with 16.04 and already hitting a wall. I am trying to change my network interface to Static from dhcp:

What am I doing wrong?

Re: Failed to start Raise network interfaces.

Nothing. I have seen the same that sometimes trying to restart the networking service doesn’t work. Reboot the machine and it will have the static IP after reboot (it should. ).

Alternatively for the restart service command try (sudo in front if not running as root):

It should be the same as what you tried, but this way sometimes works better.

Re: Failed to start Raise network interfaces.

Maybe I should go back to 14.04, not used to this stuff not working out of the box

Last edited by Heeter; November 20th, 2016 at 01:06 AM .

Re: Failed to start Raise network interfaces.

Sorry, can’t help with that. I have never used that service.

If all you want to do it set up hostname (FQDN) I always used only /etc/hostname and /etc/hosts. Or setting it up during installation which makes it right from the beginning.

Re: Failed to start Raise network interfaces.

I have seen this message (failed to raise network interfaces) in debian based systems very often (lately on debian stretch). Boot hangs for a while (or machine doesn’t boot at all).

Follows a quick-and-dirty workaround:

(i) changed line in /etc/network/interfaces to

iface eth$ inet manual

[with $ being number of interface]

(ii) switched off systemd networking like so:

sudo systemctl stop networking.service
sudo systemctl disable networking.service

[ignoring complaints of console about this being not in accordance with runlevel LSBs]

(iii) appended the following line to crontab [code: sudo crontab -e]:

@reboot ifconfig eth$ X.X.X.X && ifup eth$

[with X.X.X.X being your static IP address]

@reboot dhclient -r eth$ && dhclient eth$

Of course, this means taking away networking from systemd — for me this did the job apart from rendering the system darn slow @bootup or even useless.

Re: Failed to start Raise network interfaces.

Great, Thank you for this @Jesko

Re: Failed to start Raise network interfaces.

You’re welcome, Heeter. As this was no real solution as far as networking control over systemd is concerned (got the idea from the Raspberry Pi folks, and there are many more solutions around like renumbering network connections or messing around with udev rules) — is there a way to mark this issue as [BUTCHERED] ?

Re: Failed to start Raise network interfaces.

Re: Failed to start Raise network interfaces.

Thought not to start a new thread so posting here.
Scenario details
— Ubuntu 16.04
— one NIC being used on DHCP

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp
dns-name servers 127.0.0.1
up route add -net 172.25.0.0/16 gw 172.17.35.1 dev eth0
up route add -net 172.17.40.0/24 gw 172.17.35.1 dev eth0

— first of all I have this error going on

# systemctl status networking.service в—Џ networking.service — Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
в””в”Ђ50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Tue 2017-06-06 09:27:06 EEST; 8min ago
Docs: man:interfaces(5)
Process: 28964 ExecStart=/sbin/ifup -a —read-environment (code=exited, status=1/FAILURE)
Process: 28958 ExecStartPre=/bin/sh -c [ «$CONFIGURE_INTERFACES» != «no» ] && [ -n «$(ifquery —read-environment —list —exclude=lo)»
Main PID: 28964 (code=exited, status=1/FAILURE)

Jun 06 09:27:06 ubuntu-laf.laf.ro ifup[28964]: DHCPDECLINE on eth0 to 255.255.255.255 port 67 (xid=0x7421aec5)
Jun 06 09:27:06 ubuntu-laf.laf.ro ifup[28964]: Unable to obtain a lease on first try (declined). Exiting.
Jun 06 09:27:06 ubuntu-laf.laf.ro ifup[28964]: Failed to bring up eth0.
Jun 06 09:27:06 ubuntu-laf.laf.ro ifup[28964]: /etc/network/if-up.d/sendmail: 44: .: Can’t open /usr/share/sendmail/dynamic
Jun 06 09:27:06 ubuntu-laf.laf.ro ifup[28964]: run-parts: /etc/network/if-up.d/sendmail exited with return code 2
Jun 06 09:27:06 ubuntu-laf.laf.ro ifup[28964]: /sbin/ifup: post-up script failed.
Jun 06 09:27:06 ubuntu-laf.laf.ro systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 06 09:27:06 ubuntu-laf.laf.ro systemd[1]: Failed to start Raise network interfaces.
Jun 06 09:27:06 ubuntu-laf.laf.ro systemd[1]: networking.service: Unit entered failed state.
Jun 06 09:27:06 ubuntu-laf.laf.ro systemd[1]: networking.service: Failed with result ‘exit-code’.

— last but not least, how can I add two static routes on startup
up route add -net 172.25.0.0/16 gw 172.17.35.1 dev eth0
up route add -net 172.17.40.0/24 gw 172.17.35.1 dev eth0

as routing table doesn’t get them

# ip r
default via 172.17.35.254 dev eth0
172.17.35.0/24 dev eth0 proto kernel scope link src 172.17.35.107
172.18.0.0/16 dev docker0 proto kernel scope link src 172.18.0.1 linkdown

Источник

Failed to start: Raise network interfaces [SOLVED]

LESHIY.OD

New Member

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

It is very important to start the server by Monday.

aaron

Proxmox Staff Member

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].

Best regards,
Aaron

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

LESHIY.OD

New Member

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

Proxmox Staff Member

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.

Best regards,
Aaron

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

LESHIY.OD

New Member

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

aaron

Proxmox Staff Member

If you have public IP addresses redact them

Best regards,
Aaron

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

LESHIY.OD

New Member

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

aaron

Proxmox Staff Member

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.

Best regards,
Aaron

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

LESHIY.OD

New Member

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).

LESHIY.OD

New Member

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

aaron

Proxmox Staff Member

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.

Best regards,
Aaron

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

LESHIY.OD

New Member

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

Member

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

Member

José Claudio

Member

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á

Источник