Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #231782

Re: networking.service fails

Show all headers | View raw

On 2021-02-16 19:44, Dmitry Katsubo wrote:
> Dear Debian community,
>
> I am puzzled with the following problem. When my Debian 10.8 starts, the unit "networking.service" is
> marked as failed with the following reason:
>
> root@debian:~ # 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 2021-02-16 08:56:16 CET; 5h 27min ago
>       Docs: man:interfaces(5)
>    Process: 691 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
>   Main PID: 691 (code=exited, status=1/FAILURE)
>
> however network is working just fine. I looked into /usr/lib/systemd/system/networking.service where
>
> TimeoutStartSec=5min
>
> and also set a big timeout for br0 in /etc/network/interfaces:
>
> auto lo
> auto eth0
> auto eth1
> iface lo inet loopback
> auto br0
> iface br0 inet static
>          ...
>          bridge_ports eth0 eth1
>          bridge_maxwait 60
>
> but still the error occurs each time. Relative dmesg logs are:
>
> Feb 16 08:56:16 debian systemd[1]: Starting Raise network interfaces...
> Feb 16 08:56:16 debian ifup[691]: ifup: unknown interface eth0
> Feb 16 08:56:16 debian ifup[691]: ifup: unknown interface eth1
> Feb 16 08:56:16 debian ifup[691]: Waiting for br0 to get ready (MAXWAIT is 60 seconds).
> Feb 16 08:56:16 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
> Feb 16 08:56:16 debian systemd[1]: networking.service: Failed with result 'exit-code'.
> Feb 16 08:56:16 debian systemd[1]: Failed to start Raise network interfaces.
> Feb 16 08:56:16.113716 debian systemd-udevd[387]: Using default interface naming scheme 'v240'.
> Feb 16 08:56:16.113796 debian systemd-udevd[387]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
> Feb 16 08:56:16.113851 debian systemd-udevd[387]: Could not generate persistent MAC address for br0: No such file or directory
> Feb 16 08:56:16.115750 debian kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this
> Feb 16 08:56:16.115828 debian kernel: br0: port 1(eth0) entered blocking state
> Feb 16 08:56:16.115875 debian kernel: br0: port 1(eth0) entered disabled state
> Feb 16 08:56:16.115929 debian kernel: device eth0 entered promiscuous mode
> Feb 16 08:56:16.119800 debian kernel: r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw
> Feb 16 08:56:16.120198 debian kernel: Generic PHY r8169-200:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
> Feb 16 08:56:16.251795 debian kernel: br0: port 2(eth1) entered blocking state
> Feb 16 08:56:16.251990 debian kernel: br0: port 2(eth1) entered disabled state
> Feb 16 08:56:16.391879 debian kernel: br0: port 1(eth0) entered blocking state
> Feb 16 08:56:16.391913 debian kernel: br0: port 1(eth0) entered forwarding state
> Feb 16 08:56:16.516862 debian systemd[1]: Starting Hostname Service...
> Feb 16 08:56:16.539520 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
> Feb 16 08:56:16.539612 debian systemd[1]: networking.service: Failed with result 'exit-code'.
> Feb 16 08:56:16.539994 debian systemd[1]: Failed to start Raise network interfaces.
> Feb 16 08:56:16.671750 debian kernel: br0: port 3(wlan0) entered blocking state
> Feb 16 08:56:16.671808 debian kernel: br0: port 3(wlan0) entered disabled state
> Feb 16 08:56:16.671844 debian kernel: device wlan0 entered promiscuous mode
> Feb 16 08:56:16.671878 debian kernel: br0: port 3(wlan0) entered blocking state
> Feb 16 08:56:16.671912 debian kernel: br0: port 3(wlan0) entered forwarding state
> Feb 16 08:56:16.683579 debian hostapd[879]: wlan0: interface state UNINITIALIZED->ENABLED
> Feb 16 08:56:16.683579 debian hostapd[879]: wlan0: AP-ENABLED
>
> Any ideas where can I take a look? Thanks in advance!


Debian/Busteris still using Network Manager not systemd to control the 
network so I think the network.service shouldn't be used.

I don't know how many interfaces you have but you seem to be using a 
bridge to at least one of them. The network bridge would bring up the 
physical interface. The physical interface should be listed in 
interfaces as something like:

     iface eth0 inet manual

The listing of eth0 and eth1 (and even br0) may be obsolete. Try doing 
ifconfig as root to see what interfaces are actually7 active (since you 
say the network is running). These days they are frequently something 
like enp4s0.

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: networking.service fails Gary Dale <gary@extremeground.com> - 2021-02-17 06:10 +0100
  Re: networking.service fails Andrei POPESCU <andreimpopescu@gmail.com> - 2021-02-17 14:30 +0100
    Re: networking.service fails Gary Dale <gary@extremeground.com> - 2021-02-17 15:40 +0100

csiph-web