Bug#970156: systemd.socket fails with Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Transport endpoint is not connected
Michael Biebl
biebl at debian.org
Sat Sep 12 17:45:07 BST 2020
Am 12.09.20 um 13:33 schrieb Wolfgang Walter:
> Package: systemd
> Version: 246.4-1
> Severity: important
>
> Since upgrading (to 246 think) our socket services terminate sometimes every
> hour with:
>
> "Failed to queue service startup job (Maybe the service file is missing or not
> a template unit?): Transport endpoint is not connected"
>
> I think this is this bug:
>
> https://www.spinics.net/lists/systemd-devel/msg04761.html
> https://www.spinics.net/lists/systemd-devel/msg04784.html
>
> So commit 86e045ecefc404d4fccbeb78aa212ec4714a5763 should fix this.
>
> Would it be possible to include this fix into debian's systemd?
Sure. Would you be willing to confirm that this commit fixes your issue?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200912/888eb55a/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list