Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62576 - [systemd] systemd-networkd crashes

Attached to Project: Arch Linux
Opened by Andrej Podzimek (andrej) - Thursday, 09 May 2019, 01:55 GMT
Last edited by David Runge (dvzrv) - Tuesday, 19 November 2019, 23:06 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

Description:

systemd-networkd keeps crashing.

Additional info:

* package version(s)

systemd 241.0-1 works. The version probably doesn't exist. That's what makepkg came up with when I finally figured out how to build an older version.
systemd 241.93-1 most likely worked.
systemd 242.0-3 is broken.

(BTW, the PKGBUILD s*c*s tremendously. Or perhaps makepkg does, in this case, when interacting with Git. Setting 241.93 (the last known working revision) just doesn't work, because the version number gets "magically" "cleverly" overwritten. By a broken version, in this case. If the "_commit" thing has to be there, could it possibly work in such a way that the *older* of the two possibilities ("_commit" or "version.some_weird_commit_sequential_number") gets picked? Yes, I may be ranting about it too much, but because it took me >an hour of downtime to figure this out, I feel like ranting at the moment. It should be easier to downgrade a broken package.)

* config and/or log files etc.

May 09 02:08:30 charon systemd[1]: Starting Network Service...
May 09 02:08:31 charon systemd-networkd[1527]: /etc/systemd/network/01-charonwifi0_0.network:22: Found prefix [censored]:3::/64
May 09 02:08:31 charon systemd-networkd[1527]: /etc/systemd/network/01-charonwifi0.network:22: Found prefix [censored]:2::/64
May 09 02:08:31 charon systemd-networkd[1527]: /etc/systemd/network/00-charonbr0.network:24: Found prefix [censored]:4::/64
May 09 02:08:31 charon systemd-networkd[1527]: /etc/systemd/network/00-charon10g1.network:25: Found prefix [censored]:1::/64
May 09 02:08:31 charon systemd-networkd[1527]: charonbr0: netdev ready
May 09 02:08:31 charon systemd-networkd[1527]: Enumeration completed
May 09 02:08:31 charon systemd[1]: Started Network Service.
May 09 02:08:31 charon systemd-networkd[1527]: charon1g0: Interface name change detected, charon1g0 has been renamed to eth0.
May 09 02:08:31 charon systemd-networkd[1527]: charon1g1: Interface name change detected, charon1g1 has been renamed to eth1.
May 09 02:08:31 charon systemd-networkd[1527]: eth0: Interface name change detected, eth0 has been renamed to charon1g0.
May 09 02:08:31 charon systemd-networkd[1527]: eth1: Interface name change detected, eth1 has been renamed to charon1g1.
May 09 02:08:31 charon systemd-networkd[1527]: enp0s20u1u2u4: Interface name change detected, enp0s20u1u2u4 has been renamed to eth0.
May 09 02:08:31 charon systemd-networkd[1527]: eth0: Interface name change detected, eth0 has been renamed to enp0s20u1u2u4.
May 09 02:08:31 charon systemd-networkd[1527]: charonwifi1: Interface name change detected, charonwifi1 has been renamed to wlan0.
May 09 02:08:31 charon systemd-networkd[1527]: wlan0: Interface name change detected, wlan0 has been renamed to charonwifi1.
May 09 02:08:31 charon systemd-networkd[1527]: charon10g0: Interface name change detected, charon10g0 has been renamed to eth0.
May 09 02:08:31 charon systemd-networkd[1527]: charonwifi0: Interface name change detected, charonwifi0 has been renamed to wlan0.
May 09 02:08:31 charon systemd-networkd[1527]: wlan0: Interface name change detected, wlan0 has been renamed to charonwifi0.
May 09 02:08:31 charon systemd-networkd[1527]: charon10g1: Interface name change detected, charon10g1 has been renamed to eth1.
May 09 02:08:31 charon systemd-networkd[1527]: eth1: Interface name change detected, eth1 has been renamed to charon10g1.
May 09 02:08:31 charon systemd-networkd[1527]: eth0: Interface name change detected, eth0 has been renamed to charon10g0.
May 09 02:08:32 charon systemd-networkd[1527]: charonbr0: Could not bring up interface: Invalid argument
May 09 02:08:32 charon systemd-networkd[1527]: charon1g0: Configured
May 09 02:08:32 charon systemd-networkd[1527]: charon1g1: Configured
May 09 02:08:32 charon systemd-networkd[1527]: charonwifi0: Could not bring up interface: Invalid argument
May 09 02:08:32 charon systemd-networkd[1527]: charon10g1: Could not bring up interface: Invalid argument
May 09 02:08:33 charon systemd-networkd[1527]: charon10g0: Could not bring up interface: Invalid argument
May 09 02:08:35 charon systemd-networkd[1527]: charonwifi0: Gained carrier
May 09 02:08:35 charon systemd-networkd[1527]: charonwifi0_0: Gained carrier
May 09 02:08:35 charon systemd-networkd[1527]: Assertion 'link->network' failed at ../systemd-stable/src/network/networkd-link.c:1858, function link_acquire_ipv4_conf(). Aborting.
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Failed with result 'core-dump'.
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
May 09 02:08:36 charon systemd[1]: Stopped Network Service.
May 09 02:08:36 charon systemd[1]: Starting Network Service...
May 09 02:08:36 charon systemd-networkd[1799]: /etc/systemd/network/01-charonwifi0_0.network:22: Found prefix [censored]:3::/64
May 09 02:08:36 charon systemd-networkd[1799]: /etc/systemd/network/01-charonwifi0.network:22: Found prefix [censored]:2::/64
May 09 02:08:36 charon systemd-networkd[1799]: /etc/systemd/network/00-charonbr0.network:24: Found prefix [censored]:4::/64
May 09 02:08:36 charon systemd-networkd[1799]: /etc/systemd/network/00-charon10g1.network:25: Found prefix [censored]:1::/64
May 09 02:08:36 charon systemd-networkd[1799]: charonbr0: netdev ready
May 09 02:08:36 charon systemd-networkd[1799]: charonwifi0: Gained IPv6LL
May 09 02:08:36 charon systemd-networkd[1799]: Assertion 'link->radv' failed at ../systemd-stable/src/network/networkd-link.c:1839, function link_acquire_ipv6_conf(). Aborting.
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Failed with result 'core-dump'.
May 09 02:08:36 charon systemd[1]: Failed to start Network Service.
May 09 02:08:36 charon systemd[1]: systemd-networkd.service: Service has no hold-off time (RestartSec=0), scheduling restart.

* link to upstream bug report, if any

This might be related to / duplicate of https://bugs.archlinux.org/task/62505
It may also be related to / duplicate of https://github.com/systemd/systemd/issues/12452

Steps to reproduce:

Dunno. Just try anything less trivial than a single-interface desktop configuration. Maybe a scenario where one interaface is a WAN (but systemd-networkd must be limited to IPv4 there, because it doesn't support DHCPv6 (no, it really doesn't; it may think it does, but it just doesn't)) and other ~5 interfaces are various LANs (hostapd-based WiFi APs, 4-port network cards and the like). It will crash / fail in a weird way. This is 100% reproducible, I think. Tried to restart systemd-networkd ~100 times, but it just didn't work.
This task depends upon

Comment by loqs (loqs) - Thursday, 09 May 2019, 13:07 GMT
 FS#62483 
Edit:
PKGBUILD.patch is the diff applying the fixes for  FS#62483 
src.tar.gz has the patch applied for easy build testing.
If you still have issues please post updated journal output.
Comment by Mateusz Paluszkiewicz (TheAifam5) - Saturday, 11 May 2019, 18:03 GMT
I don't have that issue.

local/systemd 242.19-1 (base-devel)
system and service manager
local/systemd-libs 242.19-1
systemd client libraries
local/systemd-sysvcompat 242.19-1 (base)
sysvinit compat for systemd


● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-05-11 17:03:30 CEST; 2h 56min ago
Docs: man:systemd-networkd.service(8)
Main PID: 470 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
Memory: 4.6M
CGroup: /system.slice/systemd-networkd.service
└─470 /usr/lib/systemd/systemd-networkd

May 11 17:03:30 pussy-destroyer systemd-networkd[470]: eth0: Interface name change detected, eth0 has been renamed to enp109s0.
May 11 17:03:31 pussy-destroyer systemd-networkd[470]: wlan0: Interface name change detected, wlan0 has been renamed to wlp112s0.
May 11 17:03:31 pussy-destroyer systemd-networkd[470]: vmnet1: Gained carrier
May 11 17:03:31 pussy-destroyer systemd-networkd[470]: vmnet8: Gained carrier
May 11 17:03:33 pussy-destroyer systemd-networkd[470]: vmnet1: Gained IPv6LL
May 11 17:03:33 pussy-destroyer systemd-networkd[470]: vmnet8: Gained IPv6LL
May 11 17:04:03 pussy-destroyer systemd-networkd[470]: wlp112s0: Gained carrier
May 11 17:04:05 pussy-destroyer systemd-networkd[470]: wlp112s0: Gained IPv6LL
May 11 17:20:32 pussy-destroyer systemd-networkd[470]: wlp112s0: Lost carrier
May 11 17:20:33 pussy-destroyer systemd-networkd[470]: wlp112s0: Gained carrier
Comment by Christian Hesse (eworm) - Wednesday, 20 November 2019, 08:24 GMT
Is this still an issue? We fixed some systemd-networkd issues intermittently.

Loading...