Hm, I think we do have enough evidence to link the two problems.
Nick pinged me to let me know that he'd prepared a PPA with the backported upstream patch, and asked if I could test it on horsea. I did that, and verified that the new systemd package fixes the problem:
ubuntu@node-horsea:~$ sudo systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-08-04 18:47:55 UTC; 2min 35s ago
Docs: man:sshd(8) man:sshd_config(5)
Process: 884 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Main PID: 901 (sshd)
Tasks: 1 (limit: 38215)
Memory: 7.7M
CPU: 84ms
CGroup: /system.slice/ssh.service
└─901 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
Aug 04 18:47:55 node-horsea systemd[1]: Starting OpenBSD Secure Shell server...
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on 0.0.0.0 port 22.
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on :: port 22.
Aug 04 18:47:55 node-horsea systemd[1]: Started OpenBSD Secure Shell server.
Aug 04 18:50:25 node-horsea sshd[1167]: Accepted publickey for ubuntu from 10.172.68.194 port 42610 ssh2: RSA SHA256:7JLFXGJ/lkuhcSu8/OF8mHjZ8wMD1zEfNSuNGM5u2Lk
Aug 04 18:50:25 node-horsea sshd[1167]: pam_unix(sshd:session): session opened for user ubuntu(uid=1000) by (uid=0)
ubuntu@node-horsea:~$ sudo systemctl daemon-reexec
ubuntu@node-horsea:~$ sudo systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-08-04 18:47:55 UTC; 2min 41s ago
Docs: man:sshd(8) man:sshd_config(5)
Main PID: 901 (sshd)
Tasks: 1 (limit: 38215)
Memory: 7.6M
CPU: 84ms
CGroup: /system.slice/ssh.service
└─901 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
Aug 04 18:47:55 node-horsea systemd[1]: Starting OpenBSD Secure Shell server...
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on 0.0.0.0 port 22.
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on :: port 22.
Aug 04 18:47:55 node-horsea systemd[1]: Started OpenBSD Secure Shell server.
Aug 04 18:50:25 node-horsea sshd[1167]: Accepted publickey for ubuntu from 10.172.68.194 port 42610 ssh2: RSA SHA256:7JLFXGJ/lkuhcSu8/OF8mHjZ8wMD1zEfNSuNGM5u2Lk
Aug 04 18:50:25 node-horsea sshd[1167]: pam_unix(sshd:session): session opened for user ubuntu(uid=1000) by (uid=0)
I will mark bug #2004551 as a duplicate of this one. I can also help with the SRU verification, Nick. Just let me know.
Hm, I think we do have enough evidence to link the two problems.
Nick pinged me to let me know that he'd prepared a PPA with the backported upstream patch, and asked if I could test it on horsea. I did that, and verified that the new systemd package fixes the problem:
ubuntu@ node-horsea: ~$ sudo systemctl status ssh system/ ssh.service; enabled; vendor preset: enabled)
man: sshd_config( 5) /usr/sbin/ sshd -t (code=exited, status=0/SUCCESS) slice/ssh. service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/
Active: active (running) since Fri 2023-08-04 18:47:55 UTC; 2min 35s ago
Docs: man:sshd(8)
Process: 884 ExecStartPre=
Main PID: 901 (sshd)
Tasks: 1 (limit: 38215)
Memory: 7.7M
CPU: 84ms
CGroup: /system.
└─901 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
Aug 04 18:47:55 node-horsea systemd[1]: Starting OpenBSD Secure Shell server... 7JLFXGJ/ lkuhcSu8/ OF8mHjZ8wMD1zEf NSuNGM5u2Lk sshd:session) : session opened for user ubuntu(uid=1000) by (uid=0) node-horsea: ~$ sudo systemctl daemon-reexec node-horsea: ~$ sudo systemctl status ssh system/ ssh.service; enabled; vendor preset: enabled)
man: sshd_config( 5) slice/ssh. service
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on 0.0.0.0 port 22.
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on :: port 22.
Aug 04 18:47:55 node-horsea systemd[1]: Started OpenBSD Secure Shell server.
Aug 04 18:50:25 node-horsea sshd[1167]: Accepted publickey for ubuntu from 10.172.68.194 port 42610 ssh2: RSA SHA256:
Aug 04 18:50:25 node-horsea sshd[1167]: pam_unix(
ubuntu@
ubuntu@
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/
Active: active (running) since Fri 2023-08-04 18:47:55 UTC; 2min 41s ago
Docs: man:sshd(8)
Main PID: 901 (sshd)
Tasks: 1 (limit: 38215)
Memory: 7.6M
CPU: 84ms
CGroup: /system.
└─901 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
Aug 04 18:47:55 node-horsea systemd[1]: Starting OpenBSD Secure Shell server... 7JLFXGJ/ lkuhcSu8/ OF8mHjZ8wMD1zEf NSuNGM5u2Lk sshd:session) : session opened for user ubuntu(uid=1000) by (uid=0)
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on 0.0.0.0 port 22.
Aug 04 18:47:55 node-horsea sshd[901]: Server listening on :: port 22.
Aug 04 18:47:55 node-horsea systemd[1]: Started OpenBSD Secure Shell server.
Aug 04 18:50:25 node-horsea sshd[1167]: Accepted publickey for ubuntu from 10.172.68.194 port 42610 ssh2: RSA SHA256:
Aug 04 18:50:25 node-horsea sshd[1167]: pam_unix(
I will mark bug #2004551 as a duplicate of this one. I can also help with the SRU verification, Nick. Just let me know.
Thanks.