FS#56973 - [systemd] systemd-networkd crashes in systemd 236.0-2
Attached to Project:
Arch Linux
Opened by A Web (aweb) - Saturday, 06 January 2018, 06:45 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 07 January 2018, 02:02 GMT
Opened by A Web (aweb) - Saturday, 06 January 2018, 06:45 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 07 January 2018, 02:02 GMT
|
Details
Description:
After upgrading to systemd 236.0-2 from 235.38-4, systemd-networkd started crashing on bootup, and none of my network interfaces work. Reverting systemd solves the problem. Additional info: * package version(s) systemd-236.0-2 * config and/or log files etc. These are the last lines that happen before the crash: Jan 05 22:15:16 garage.uun.org systemd-networkd[679]: rtnl: received address with invalid family 129, ignoring. Jan 05 22:15:16 garage.uun.org systemd-networkd[679]: rtnl: received address with invalid family 128, ignoring. Jan 05 22:15:16 garage.uun.org systemd[1]: systemd-networkd.service: Main process exited, code=killed, status=11/SEGV Jan 05 22:15:16 garage.uun.org systemd[1]: systemd-networkd.service: Failed with result 'signal'. Jan 05 22:15:16 garage.uun.org systemd[1]: Failed to start Network Service. Jan 05 22:15:16 garage.uun.org systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Jan 05 22:15:16 garage.uun.org systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. Jan 05 22:15:16 garage.uun.org systemd[1]: Stopped Network Service. Steps to reproduce: It's a little painful to narrow this down, because I have a complex network setup that is a pain to reproduce manually, so basically I have no network if I don't downgrade systemd. However, this could be caused by the fact that I'm using wireguard, bridges, and/or an IPv6 tunnel. Also, because of how systemd works, the configuration is spread over multiple files in /etc/systemd/network, but here they are: *** /etc/systemd/network/br0.netdev: [NetDev] Name=br0 Kind=bridge *** /etc/systemd/network/br0.network: [Match] Name=br0 [Network] Address=172.30.0.4/16 Address=2001:aaaa:bbbb::4/64 IPForward=ipv6 [Route] Gateway=2001:aaaa:bbbb::3 Destination=2001:aaaa:bbbb:30::/60 [Route] Gateway=2001:aaaa:bbbb::6 Destination=2001:aaaa:bbbb:60::/60 [Route] Gateway=2001:aaaa:bbbb::8 Destination=2001:aaaa:bbbb:80::/60 [Route] Destination=0.0.0.0/0 Gateway=172.30.0.1 Metric=4096 [Route] Destination=172.16.0.0/12 Gateway=172.30.0.1 [Route] Destination=0.0.0.0/0 Gateway=172.30.0.1 Table=252 [Route] Destination=172.30.0.0/16 Scope=link Table=252 *** /etc/systemd/network/enp2s0.network: [Match] Name=enp2s0 [Network] DHCP=ipv4 [DHCP] UseDNS=false *** /etc/systemd/network/enp3s0.network: [Match] Name=enp3s0 [Network] Bridge=br0 *** /etc/systemd/network/kvm0.netdev: [NetDev] Name=kvm0 Kind=tap [Tap] User=kvm Group=kvm *** /etc/systemd/network/kvm0.network: [Match] Name=kvm0 [Network] Bridge=br0 *** /etc/systemd/network/sixbone.netdev: [Match] [NetDev] Name=sixbone Kind=sit [Tunnel] Local=any Remote=1.2.3.4 TTL=255 *** /etc/systemd/network/sixbone.network: [Match] Name=sixbone [Network] IPForward=ipv6 [Route] Destination=::/0 |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Sunday, 07 January 2018, 02:02 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#56957
Sunday, 07 January 2018, 02:02 GMT
Reason for closing: Duplicate
Additional comments about closing:
FS#56957?FS#56957seems to depend on the kernel version, not the systemd version. The bug I'm reporting seems to depend only on the systemd version, as I've run several kernels int he meantime.FS#56957turned out to be https://github.com/systemd/systemd/issues/7797 a systemd 236 specific issue. Could you try this patch for systemd-networkd https://github.com/systemd/systemd/commit/f2c8bd2876d0171a5c1238fdfa48b415cf7cca60.patch not sure whyFS#56957only triggered under 4.14.11 possibly a change affected the order in which network devices come up.