Public bug reported:
After upgrading from 22.04 to 24.04, ssh.socket failed to start.
I have overridden ListenAddress in /etc/ssh/sshd_config.d/listenaddress.conf,
which contains:
ListenAddress 192.0.2.2
ListenAddress ::
This was converted into the following
/run/systemd/generator/ssh.socket.d/addresses.conf
# Automatically generated by sshd-socket-generator
[Socket]
ListenStream=
ListenStream=22
ListenStream=192.0.2.2:22
The two ListenStream definitions obviously conflict, causing the startup error.
Although my ListenAddress configuration doesn't do what I wanted it to either
(listen on just one v4 address but all v6 addresses), it just listens on all
addresses (*:22), sshd starts successfully with it.
As I don't need socket activation as RAM usage isn't an issue in my case, I
disabled ssh.socket and reenabled ssh.service to make it work again.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: openssh-server 1:9.6p1-3ubuntu13.5
ProcVersionSignature:
Uname: Linux 6.8.12-4-pve x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Nov 21 02:06:35 2024
ProcEnviron:
PATH=(custom, no user)
TERM=linux
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: openssh
UpgradeStatus: Upgraded to noble on 2024-11-21 (0 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089198
Title:
sshd-socket-generator incorrectly converts ListenAddress to
ListenStream, sshd does not start due to "Address already in use"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2089198/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
