[Bug 2087551] [NEW] OpenSSH server config broken on unattended update

[Chris Leonard]

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 connect to the server again:

https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
ubuntu-22-10-and-later/30189

I suspect this is related to using a non-default port, although the
systemd socket configuration appeared to exist with correct values, as
well as the custom port value in sshd_config, before making the above
change.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: openssh-server 1:9.6p1-3ubuntu13.7
ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12
Uname: Linux 6.8.0-48-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: configdrive
CloudName: configdrive
CloudPlatform: configdrive
CloudSerial: 20231014
CloudSubPlatform: config-disk (/dev/vdb)
Date: Fri Nov  8 13:13:51 2024
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=tmux-256color
SourcePackage: openssh
UpgradeStatus: Upgraded to noble on 2024-06-04 (157 days ago)

** Affects: openssh (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug cloud-image noble

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

Title:
  OpenSSH server config broken on unattended update

Status in openssh package in Ubuntu:
  New

Bug description:
  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 connect to the server again:

  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189

  I suspect this is related to using a non-default port, although the
  systemd socket configuration appeared to exist with correct values, as
  well as the custom port value in sshd_config, before making the above
  change.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu13.7
  ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12
  Uname: Linux 6.8.0-48-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: server
  CloudID: configdrive
  CloudName: configdrive
  CloudPlatform: configdrive
  CloudSerial: 20231014
  CloudSubPlatform: config-disk (/dev/vdb)
  Date: Fri Nov  8 13:13:51 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  SourcePackage: openssh
  UpgradeStatus: Upgraded to noble on 2024-06-04 (157 days ago)

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