Debian User Forums
[Solved] Failed to start raise network interfaces
[Solved] Failed to start raise network interfaces
#1 Post by Lamios » 2017-12-10 00:06
when I start Debian I get an error message saying the following:
ifconfig -a lists the following devices:
— enp0s25
— lo
— vpn0
— wlp2s0
The network had been configured automatically with DHCP during the installation.
I am still able to connect to the internet, also if I sometimes have to reboot, because I get the massage that the connection had been deactivated.
The system (Debian 9 with KDE) is newly installed and the problem existed from beginning. The results from google and forum searches did not fit to my error message (at least as far as I can asses it as a Linux beginner).
Thank you for your help!
Lamios
P.S.: I hope the post is complete for the beginning. I am not sure in the moment, which additional output is going to be needed.
Re: Failed to start raise network interfaces
p.H Section Moderator
Posts: 3049 Joined: 2017-09-17 07:12 Has thanked: 5 times Been thanked: 130 times
Re: Failed to start raise network interfaces
#3 Post by p.H » 2017-12-10 07:15
Re: Failed to start raise network interfaces
#4 Post by Lamios » 2017-12-10 11:40
Thank you for the very fast reply!
systemctl cat networking.service:
p.H Section Moderator
Posts: 3049 Joined: 2017-09-17 07:12 Has thanked: 5 times Been thanked: 130 times
Re: Failed to start raise network interfaces
#5 Post by p.H » 2017-12-10 12:11
The lines you posted are truncated.
Scripts in /etc/network/if-*.d/ are run by run-parts. By default run-parts executes all scripts with names containing only letters, digits, underscore and hyphen [A-Za-z0-9_-]. So /etc/network/if-pre-up.d/firewall is executed, but /etc/network/if-pre-up.d/firewall.save is not because its name contains a dot, not in the allowed character list.
Renaming /etc/network/if-pre-up.d/firewall by adding _renamed does not disable its execution by run-parts because all characters of the suffix are allowed. However if an instruction in the script uses an other file such as /etc/iptables.firewall.rules and you renamed that file without updating the script, then an error may arise. Check in /etc/network/if-pre-up.d/firewall_renamed.
Also note that just renaming the script and not disabling it does not prevent interference with another firewall script.
Как настроить сеть в Debian 10?
Что-то я совсем потерялся в новом Debian, который 10.
Пытаюсь настроить сеть, вроде типовая операция, но вылезла интересная проблема, точнее проблемы.
Вот конфиг interfaces:
в названиях сетевых интерфейсов ошибки нет.
Выполнил ip l:
1: lo: 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: ens32: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:0c:29:54:c1:fc brd ff:ff:ff:ff:ff:ff
3: ens33: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:0c:29:54:c1:06 brd ff:ff:ff:ff:ff:ff
Проблемы:
команда systemctl restart networking вызывает проблему:
Job for networking.service failed because the control process exited with error code.
See «systemctl status networking.service» and «journalctl -xe» for details.
Вот что в логах:
Самое интересное, что если перезагрузить компьютер, то сеть поднимается и работает нормально.
Путем проб и ошибок выяснил, что одна из ошибок — auto ens33 и auto ens32
убираю эти директивы — перезапускаю сеть systemctl restart networking — отрабатывает без проблем, но не поднимаеется интерфейс ens32.
Failed to start Raise network interfaces after upgrading to 16.04
I just upgraded a virtual 14.04 server machine to 16.04. After rebooting the VM I see the following error:
After login I can run the mentioned command and get the following output (image as I’m not able to connect):
The configuration in /etc/network/interfaces looks fine — featuring the manually configured eth0 (not using dhcp here)
What makes me wondering is that ifconfig -a lists
- ens160
- lo
Where I would expect
- eth0
- lo
Trying to up the eth0 device via
The virtual wired network device itself is still configured in the VM itself as it was before.
ip link shows as well lo and ens160 — where ens160 has the mac address configured in vmware for the single configured virtual network device.
UPDATE
I am able to solve the issue if i change all references of eth0 in /etc/network/interfaces to ens160.
BUT — this feels wrong for me for several reasons:
- I would like to understand this problem
- I would like to stick to eth0 instead of ens160
So please can someone explain this change, which didn’t happen to several other 14.04 machines on the same server which I also upgraded to 16.04.
Startup Debian 9 error: `Failed to start Raise network interfaces`
error occurres. The (cable) LAN-connection works but the (USB) WiFi is not working properly (detecting the WiFi networks but failing to connect). Previously on the same harware Debian 8 Jessie was installed working fine without any errors.
Seems the issues are connected to the recent predictable network interface names changes. Found users A, B, C, D, and E had similar symptoms. However, they had upgraded Ubuntu systems (without a clean install). Aditionally the proposed solutions are suggesting disabling the assignment of fixed/predictable/unique names. I would prefer to keep the new naming scheme/standard, eventually to find and eliminate the reason why(?) it is not working properly.
Found also users F, and G with the same problem — without solution.
Would be very thankful for any hint. Also, I’m happy to answer your questions if you need more in depth details.