[systemd-devel] Custom systemd socket fails to start after systemd/os upgrade

[Lennart Poettering]

On Fri, 05.05.17 08:22, Robert Pilja (robert.pilja at 1und1.de) wrote:

> Hello,

> i'm looking for help on debugging a systemd issue after
> upgrading our systems from RHEL 7.2 to 7.3 (systemd:
> 219-19.el7_2.9.ppc64 -> 219-30.el7_3.7.ppc64).

Upstream we generally focus on maintainance of the current upstream
versions of systemd. Please contact RHEL support for help with the
packages in RHEL which are much older, in particular when issues are
caused by package versions that do not change the upstream version.

> Apr 24 03:38:16 bscqs01.server.lan systemd[1]: commandsocket_57813 at 65309-10.88.44.62:57813-10.88.44.27:51161.service failed to run 'start' task: Transport endpoint is not connected

Hmm, this is interesting, it inda suggests that this stuff gets
confused by a client that connected but terminated the connection
before it was completed?

That all said, please make sure to use ExecStart=-/bin/sh (i.e. prefix
the command with a dash). Otherwise each failing instance of the
service will be kept around for admin introspection and that might
result in an ever growing list of loaded unit files.

Lennart

-- 
Lennart Poettering, Red Hat