> If you are able to find some error in the journal, or evidence that
ssh.socket was listening on the wrong port etc., please share it.
Sorry I have nothing, just know that it was refusing connection, and
that trying to start sshd manually with `systemctl start ssh.service`
didn't work even though
Thanks.
This has restored socket-based activation, but with a different
configuration than I had earlier, and has not reproduced the problem.
I've confirmed that this really is socket-based activation by stopping
the ssh service in the recovery console, confirming sshd is dead, and
reconnecting,
And in case it was missed: /etc/ssh/sshd_config.d/ is empty.
I can try breaking ssh again to reproduce, but I don't know sockets too
well, could you point me to some info on how to enable this? I tried
looking and can only find instructions to go the other way, apologies!
--
You received this b
Update was at 6:48 local time today.
journalctl -u ssh.socket shows the socket deactivated and came back, no
more activity until I started trying to fix things at 8:13:
Nov 08 06:48:27 www-veltas systemd[1]: ssh.socket: Deactivated successfully.
Nov 08 06:48:27 www-veltas systemd[1]: Closed ssh.s
This is shown corresponding to that unattended update with -u
ssh.service:
Nov 08 06:48:27 www-veltas sshd[1102]: Received signal 15; terminating.
Nov 08 06:48:27 www-veltas systemd[1]: Stopping ssh.service - OpenBSD Secure
Shell server...
Nov 08 06:48:27 www-veltas systemd[1]: ssh.service: Deact
/etc/ssh/sshd_config.d/ is empty
As I've said, my config is working after following the linked steps, but
unfortunately that means I don't have the systemd socket configuration
files anymore.
I'm hoping the fact that this specific update seemed to stop my ssh
service can help narrow this down.
-
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to
Public bug reported:
My server performed unattended update of openssh-server from
1:9.6p1-3ubuntu13.5 to 1:9.6p1-3ubuntu13.7, and after this I could not
access ssh anymore, connection refused.
Following the steps at the bottom of this post to use non-socket-based-
activation has allowed me to con