FS#61377 - [systemd] networkd core dumped after a docker container is finished

Attached to Project: Arch Linux
Opened by Carsten (xabbu) - Sunday, 13 January 2019, 11:51 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 13:26 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

systemd-networkd core dumped after a docker container is finished. It started with systemd 240.0-3 and is still present in 240.34-2. networkd restarts after the core dump. The docker version is 1:18.09.1-1.
It happens with containers which stops very quickly after the start. The container form the log below ran around 3 seconds until it was finished. I did not see this problem with long running container.
The networkd error message is

Assertion 'link->manager' failed at ../systemd-stable/src/network/networkd-link.c:3079, function link_initialized_and_synced(). Aborting

Additional info:
systemd 240.34-2
docker 1:18.09.1-1

Jan 13 11:05:03 xabbu systemd-networkd[19838]: veth68de3cc: Lost carrier
Jan 13 11:05:03 xabbu kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:03 xabbu systemd-udevd[20838]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 13 11:05:03 xabbu kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:03 xabbu kernel: device veth68de3cc left promiscuous mode
Jan 13 11:05:03 xabbu kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:04 xabbu systemd-networkd[19838]: Assertion 'link->manager' failed at ../systemd-stable/src/network/networkd-link.c:3079, function link_initialized_and_synced(). Aborting.
Jan 13 11:05:04 xabbu systemd[1]: Started Process Core Dump (PID 21152/UID 0).
Jan 13 11:05:04 xabbu systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT
Jan 13 11:05:04 xabbu systemd[1]: systemd-networkd.service: Failed with result 'core-dump'.
Jan 13 11:05:04 xabbu systemd[1]: systemd-networkd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Jan 13 11:05:04 xabbu systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 11.
Jan 13 11:05:04 xabbu systemd[1]: systemd-networkd-wait-online.service: Succeeded.
Jan 13 11:05:04 xabbu systemd[1]: Stopped Wait for Network to be Configured.
Jan 13 11:05:04 xabbu systemd[1]: Stopping Wait for Network to be Configured...
Jan 13 11:05:04 xabbu systemd[1]: Stopped Network Service.
Jan 13 11:05:04 xabbu systemd[1]: Starting Network Service...
Jan 13 11:05:04 xabbu systemd-coredump[21153]: Process 19838 (systemd-network) of user 981 dumped core.

Stack trace of thread 19838:
#0 0x00007fe767e6cd7f raise (libc.so.6)
#1 0x00007fe767e57672 abort (libc.so.6)
#2 0x00007fe767bf202c n/a (libsystemd-shared-240.so)
#3 0x00005612a1ac49e2 n/a (systemd-networkd)
#4 0x00005612a1ac61ec n/a (systemd-networkd)
#5 0x00007fe767c2f4d7 sd_netlink_process (libsystemd-shared-240.so)
#6 0x00007fe767c2f7d4 n/a (libsystemd-shared-240.so)
#7 0x00007fe767c22220 n/a (libsystemd-shared-240.so)
#8 0x00007fe767c22511 sd_event_dispatch (libsystemd-shared-240.so)
#9 0x00007fe767c226d9 sd_event_run (libsystemd-shared-240.so)
#10 0x00007fe767c228fc sd_event_loop (libsystemd-shared-240.so)
#11 0x00005612a1a9b288 n/a (systemd-networkd)
#12 0x00007fe767e59223 __libc_start_main (libc.so.6)
#13 0x00005612a1a9be2e n/a (systemd-networkd)
Jan 13 11:05:04 xabbu systemd[1]: systemd-coredump@10-21152-0.service: Succeeded.
Jan 13 11:05:05 xabbu systemd-networkd[21170]: docker0: Gained IPv6LL
Jan 13 11:05:05 xabbu systemd-networkd[21170]: eth0: Gained IPv6LL
Jan 13 11:05:05 xabbu systemd-networkd[21170]: Enumeration completed
Jan 13 11:05:05 xabbu systemd[1]: Started Network Service.


This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 10 December 2019, 13:26 GMT
Reason for closing:  Fixed
Comment by Dave Reisner (falconindy) - Sunday, 13 January 2019, 13:23 GMT Comment by Carsten (xabbu) - Sunday, 13 January 2019, 19:41 GMT
The upstream bug report
https://github.com/systemd/systemd/issues/11411

It looks like PR 11412 fixes the problem.
https://github.com/systemd/systemd/pull/11412
Comment by nfnty (nfnty) - Wednesday, 13 February 2019, 05:00 GMT
I'm hitting a similar issue: https://github.com/systemd/systemd/issues/11272

Fixed by: https://github.com/systemd/systemd/pull/11274

Can both PR #11272 and #11412 be backported? Networkd is crashing repeatedly here.
Comment by Carsten (xabbu) - Wednesday, 13 February 2019, 10:11 GMT
PR #11412 is part of 240.93 and 240.95

This Bug Report can be closed.

I don't think PR #11272 was added to systemd-stable yet.
https://github.com/systemd/systemd-stable/pull/40

Loading...