> but with a different configuration than I had earlier

Different in what way?

I am glad this restored socket-activation for you. I am not sure how to
further investigate the bug. 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.

Did you happen to check systemctl status ssh.socket ssh.service (or
something) before making the change to non-socket activation?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087551

Title:
  OpenSSH server config broken on unattended update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2087551/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to