0

I'm having issues with systemd-networkd on a newly set-up server which has 2 NICs w/ 4 ports each installed. I haven't touched any networkd configuration (aside from debug-level logging today), and only defined my network in the netplan (cloud-init) configuration /etc/netplan/50-cloud-init.yaml.

The Problem

After systemctl restart systemd-networkd is called (ie. on systemd updates), the server can not be reached via network anymore. Pings fail from/to the server, with exception of the gateway. 127.0.0.1 can still be pinged and ip route shows exactly the same routing table before and after.

Only a reboot solves the problem, I tried netplan apply after restarting networkd without success.

Observations & Info

Pings to other hosts fail with error "No route to host".

After systemd-networkd was restarted, the console logged network interface changes, stating the link speed was set to 0.

The routing table as returned by ip route remains untouched after networkd restart, as well as IP configuration of the interfaces.

All ports on the 2nd NIC are using LLCP Link bonding with a compatible switch. Other NICs are also connected to the same switch. Addresses are managed by a DHCP on the network.

Logs

Debug log of systemd-networkd restart: https://pastebin.com/9bp38r0b

The only unusual thing I noticed was networkd ignores config files (written by netplan?), but this occurs on a clean boot too:

-- Reboot --
Jul 24 08:55:27 skprov2 systemd[1]: Starting Network Service...
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Bus n/a: changing state UNSET → OPENING
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Added inotify watch for /run on bus n/a: 2
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Added inotify watch for /run/dbus on bus n/a: -1
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Bus n/a: changing state OPENING → WATCH_BIND
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: timestamp of '/etc/systemd/network' changed
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: timestamp of '/run/systemd/network' changed
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /run/systemd/network/10-netplan-bcm.network, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /run/systemd/network/10-netplan-bond0.network, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /run/systemd/network/10-netplan-intel.network, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /lib/systemd/network/80-container-vz.network, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /lib/systemd/network/80-container-ve.network, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /lib/systemd/network/80-container-host0.network, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .netdev.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: bond0: loaded bond
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: bond0: Creating
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /run/systemd/network/10-netplan-bond0.netdev, because it's not a regular file with suffix .network.
Jul 24 08:55:27 skprov2 systemd-networkd[1014]: Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .network.

What exactly is causing this issue? I'd like to use this server as a stable production machine. I encountered this issue some weeks ago, and now again because the systemd package was upgraded.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.