Dear Maintainer,
I ran into a problem by calling 'systemctl start ssh.service; systemctl enable ssh.service'.
My observation was that the ssh.service was in state 'inactive (dead)' even though
it was running. systemctl status still showed the correct MainPID and the process
in the cgroup.
This is reproducible (always resetted to a snapshot of a VM) in about 50% of my tries.
I once even ran into an ABRT in src/core/service.c service_sigchld_event() state switch,
pointing to an invalid state (default: assert_not_reached()), I unfortunately have
no backtrace of this.
The 'systemctl enable' command triggers a daemon-reload.
I think this is related to upstream bug https://github.com/systemd/systemd/pull/39703 .
ssh.service has alias sshd.service, which might be the cause of the problem.
This fix is backported to the upstream v258-stable branch and newer, but not to v257,
as this is probably too old.
I would like to have this patch added to the debian patches to fix the issue.