On Mo, 07.09.20 14:22, Alec Moskvin ([email protected]) wrote: > A few days ago I tried to ssh into one of my boxes (which was using > socket-activated per-connection ssh) but got connection refused. Luckily > I had another ssh session open. In the journal, the only relevant thing > logged was: > > systemd[1]: sshd.socket: Failed to queue service startup job (Maybe the > service file is missing or not a template unit?): Transport endpoint is not > connected > systemd[1]: sshd.socket: Failed with result 'resources'. > > I started the socket back up and could connect again. The system had > been mostly idle and there were no upgrades since it booted up 2 days > earlier. The previous ssh login attempt was 4 hours before.
It's a bug. Should be fixed by 86e045ecefc404d4fccbeb78aa212ec4714a5763. Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
