Bug#879603: systemd: network service enters failed state when client goes away too fast

Julien Cristau jcristau at debian.org
Mon Oct 23 11:21:28 BST 2017


Package: systemd
Version: 232-25+deb9u1
User: debian-admin at lists.debian.org
Usertag: needed-by-DSA-Team

It looks like systemd has a race condition where instead of giving up
gracefully when a client goes away, it enters a bogus failure mode.

● vsftpd-security at 9330-149.20.4.14:21-X.X.X.X:Y.service - vsftpd security
   Loaded: loaded (/etc/systemd/system/vsftpd-security at .service; static;
vendor preset: enabled)
   Active: failed (Result: resources)

Oct 22 18:48:41 mirror-isc systemd[1]:
vsftpd-security at 9330-149.20.4.14:21-X.X.X.X:Y.service: Failed to run
'start' task: Transport endpoint is not connected
Oct 22 18:48:41 mirror-isc systemd[1]: Failed to start vsftpd security.
Oct 22 18:48:41 mirror-isc systemd[1]:
vsftpd-security at 9330-149.20.4.14:21-X.X.X.X:Y.service: Unit entered
failed state.
Oct 22 18:48:41 mirror-isc systemd[1]:
vsftpd-security at 9330-149.20.4.14:21-X.X.X.X:Y.service: Failed with
result 'resources'.

Cheers,
Julien



More information about the Pkg-systemd-maintainers mailing list