[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
Seems this has now made its way downstream to openssh-server 9.0 (on a different box): The following packages will be upgraded: openssh-client openssh-server openssh-sftp-server 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1295 kB of archives. After this operation, 65.5 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ca.ports.ubuntu.com/ubuntu-ports lunar-proposed/main arm64 openssh-sftp-server arm64 1:9.0p1-1ubuntu8.2 [36.0 kB] Get:2 http://ca.ports.ubuntu.com/ubuntu-ports lunar-proposed/main arm64 openssh-server arm64 1:9.0p1-1ubuntu8.2 [409 kB] Get:3 http://ca.ports.ubuntu.com/ubuntu-ports lunar-proposed/main arm64 openssh-client arm64 1:9.0p1-1ubuntu8.2 [849 kB] Fetched 1295 kB in 1s (921 kB/s) Preconfiguring packages ... (Reading database ... 104735 files and directories currently installed.) Preparing to unpack .../openssh-sftp-server_1%3a9.0p1-1ubuntu8.2_arm64.deb ... Unpacking openssh-sftp-server (1:9.0p1-1ubuntu8.2) over (1:9.0p1-1ubuntu8.1) ... Preparing to unpack .../openssh-server_1%3a9.0p1-1ubuntu8.2_arm64.deb ... Unpacking openssh-server (1:9.0p1-1ubuntu8.2) over (1:9.0p1-1ubuntu8.1) ... Preparing to unpack .../openssh-client_1%3a9.0p1-1ubuntu8.2_arm64.deb ... Unpacking openssh-client (1:9.0p1-1ubuntu8.2) over (1:9.0p1-1ubuntu8.1) ... Setting up openssh-client (1:9.0p1-1ubuntu8.2) ... Setting up openssh-sftp-server (1:9.0p1-1ubuntu8.2) ... Setting up openssh-server (1:9.0p1-1ubuntu8.2) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.11.2-1) ... Processing triggers for ufw (0.36.1-4.1) ... Errors were encountered while processing: openssh-server needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Should I cut a new bug for this? It's a different arch and a different version of Ubuntu, but it's the exact same symptom (and, likely, cause). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session Status in openssh package in Ubuntu: Fix Committed Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
Seems fixed. Huzzah! $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu3 Candidate: 1:9.2p1-2ubuntu3 Version table: *** 1:9.2p1-2ubuntu3 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session Status in openssh package in Ubuntu: Fix Committed Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
Still an issue in the latest version: Setting up openssh-server (1:9.2p1-2ubuntu2) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Setting up sosreport (4.5.3ubuntu2) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for ufw (0.36.2-1) ... Errors were encountered while processing: openssh-server needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) scottfk@venus2:~$ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu2 Candidate: 1:9.2p1-2ubuntu2 Version table: *** 1:9.2p1-2ubuntu2 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages Re: Workaround, adding this to root's crontab sorted me: @reboot dpkg --configure -a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session Status in openssh package in Ubuntu: Confirmed Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation
root@venus2:/etc/systemd/system/ssh.service.d# /usr/sbin/sshd -d debug1: sshd version OpenSSH_9.2, OpenSSL 3.0.8 7 Feb 2023 debug1: private host key #0: ssh-rsa SHA256:jBRj9thNiN3QA5SVICY9H4/b2f2tvIqyKv2krB+q1+E debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:+AoeQEDs9PNiD54EnDi/YTJksSDND59lJqCe5BAgdz0 debug1: private host key #2: ssh-ed25519 SHA256:fJj+sS6kyWxB/3Z36XR7DE7J1w9TYvR8GLRT0Kr+DNU debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-d' debug1: Set /proc/self/oom_score_adj from 0 to -1000 debug1: Bind to port 22 on 0.0.0.0. Bind to port 22 on 0.0.0.0 failed: Address already in use. debug1: Bind to port 22 on ::. Bind to port 22 on :: failed: Address already in use. Cannot bind any address. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 fails post-installation Status in openssh package in Ubuntu: Incomplete Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation
root@venus2:/home/scottfk# systemctl restart ssh.socket Job failed. See "journalctl -xe" for details. May 23 20:36:21 venus2 systemd[2014]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit ssh.socket has entered the 'failed' state with result 'resources'. May 23 20:36:21 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. ░░ Subject: A start job for unit ssh.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit ssh.socket has finished with a failure. ░░ ░░ The job identifier is 1542 and the job result is failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 fails post-installation Status in openssh package in Ubuntu: Incomplete Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+subscriptions -- Mailing l
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation
So I tried this in an amd64 VM. Installing this version of openssh- server (from inside a GNOME session) worked just fine. ssh-ing to localhost and attempting a reinstall ended up in the exact same FAIL. So it seems the upgrade of openssh-server 1:9.2p1-2ubuntu1 can't be done from an ssh session (regardless of processor architecture). I'll do more poking around to see if I can't figure out why systemd won't/can't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 fails post-installation Status in openssh package in Ubuntu: Incomplete Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation
Before retriggering the post-installation:
root@venus2:/home/scottfk# systemctl status 904
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
└─00-socket.conf
Active: active (running) since Tue 2023-05-23 15:17:36 CEST; 4h 40min ago
TriggeredBy: ● ssh.socket
Docs: man:sshd(8)
man:sshd_config(5)
Main PID: 904 (sshd)
Tasks: 1 (limit: 9378)
Memory: 5.1M
CPU: 468ms
CGroup: /system.slice/ssh.service
└─904 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
May 23 15:17:35 venus2 systemd[1]: Starting ssh.service - OpenBSD Secure Shell
server...
May 23 15:17:36 venus2 sshd[904]: Server listening on :: port 22.
May 23 15:17:36 venus2 systemd[1]: Started ssh.service - OpenBSD Secure Shell
server.
May 23 15:17:36 venus2 sshd[905]: Accepted publickey for scottfk from
2a02:1210:2a23:5600:9e82:2fb7:9772:3bf6 port 4092>
May 23 15:17:36 venus2 sshd[905]: pam_unix(sshd:session): session opened for
user scottfk(uid=1000) by (uid=0)
root@venus2:/home/scottfk# systemctl status 905
● session-2.scope - Session 2 of User scottfk
Loaded: loaded (/run/systemd/transient/session-2.scope; transient)
Transient: yes
Active: active (running) since Tue 2023-05-23 15:17:37 CEST; 4h 41min ago
Tasks: 8
Memory: 18.2M
CPU: 4.330s
CGroup: /user.slice/user-1000.slice/session-2.scope
├─ 905 "sshd: scottfk [priv]"
├─ 997 "sshd: scottfk@pts/0"
├─ 998 -bash
├─1113 sudo bash -o vi
├─1114 sudo bash -o vi
├─1115 bash -o vi
├─1301 systemctl status 905
└─1302 less
May 23 15:17:37 venus2 systemd[1]: Started session-2.scope - Session 2 of User
scottfk.
May 23 15:17:41 venus2 sshd[905]: pam_env(sshd:session): deprecated reading of
user environment enabled
May 23 17:41:33 venus2 sudo[1108]: scottfk : TTY=pts/0 ; PWD=/home/scottfk ;
USER=root ; COMMAND=/usr/bin/lsof -i :22
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session opened for
user root(uid=0) by scottfk(uid=1000)
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session closed for
user root
May 23 17:42:20 venus2 sudo[1113]: scottfk : TTY=pts/0 ; PWD=/home/scottfk ;
USER=root ; COMMAND=/usr/bin/bash -o vi
May 23 17:42:20 venus2 sudo[1113]: pam_unix(sudo:session): session opened for
user root(uid=0) by scottfk(uid=1000)
root@venus2:/home/scottfk# systemctl status 997
● session-2.scope - Session 2 of User scottfk
Loaded: loaded (/run/systemd/transient/session-2.scope; transient)
Transient: yes
Active: active (running) since Tue 2023-05-23 15:17:37 CEST; 4h 41min ago
Tasks: 8
Memory: 18.3M
CPU: 4.376s
CGroup: /user.slice/user-1000.slice/session-2.scope
├─ 905 "sshd: scottfk [priv]"
├─ 997 "sshd: scottfk@pts/0"
├─ 998 -bash
├─1113 sudo bash -o vi
├─1114 sudo bash -o vi
├─1115 bash -o vi
├─1304 systemctl status 997
└─1305 less
May 23 15:17:37 venus2 systemd[1]: Started session-2.scope - Session 2 of User
scottfk.
May 23 15:17:41 venus2 sshd[905]: pam_env(sshd:session): deprecated reading of
user environment enabled
May 23 17:41:33 venus2 sudo[1108]: scottfk : TTY=pts/0 ; PWD=/home/scottfk ;
USER=root ; COMMAND=/usr/bin/lsof -i :22
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session opened for
user root(uid=0) by scottfk(uid=1000)
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session closed for
user root
May 23 17:42:20 venus2 sudo[1113]: scottfk : TTY=pts/0 ; PWD=/home/scottfk ;
USER=root ; COMMAND=/usr/bin/bash -o vi
May 23 17:42:20 venus2 sudo[1113]: pam_unix(sudo:session): session opened for
user root(uid=0) by scottfk(uid=1000)
Retriggering the post-installation:
root@venus2:/home/scottfk# dpkg --configure -a
Setting up openssh-server (1:9.2p1-2ubuntu1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
openssh-server
root@venus2:/home/scottfk# systemctl status 904
Failed to get unit for PID 904: PID 904 does not belong to any loaded unit.
root@venus2:/home/scottfk# systemctl status 905
● session-2.scope - Session 2 of User scottfk
Loaded: loaded (/run/systemd/transient/session-2.scope; transient)
Transient: yes
Active: active (running) since Tue 2023-05-23 15:17:37 CEST; 4h 43min ago
Tasks: 8
Memory: 33.6M
CPU: 9.657s
CGroup: /user.slice/user-1000.sli
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation
# lsof -i :22 COMMAND PIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1root 140u IPv6 22354 0t0 TCP *:ssh (LISTEN) sshd904root3u IPv6 22354 0t0 TCP *:ssh (LISTEN) sshd905root3u IPv6 22354 0t0 TCP *:ssh (LISTEN) sshd905root4u IPv6 18405 0t0 TCP venus2.home:ssh->hydra.home:40926 (ESTABLISHED) sshd905root5u IPv6 18405 0t0 TCP venus2.home:ssh->hydra.home:40926 (ESTABLISHED) sshd 997 scottfk3u IPv6 22354 0t0 TCP *:ssh (LISTEN) sshd 997 scottfk4u IPv6 18405 0t0 TCP venus2.home:ssh->hydra.home:40926 (ESTABLISHED) sshd997 scottfk5u IPv6 18405 0t0 TCP venus2.home:ssh->hydra.home:40926 (ESTABLISHED) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 fails post-installation Status in openssh package in Ubuntu: Incomplete Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation
This is just the out-of-the-box sshd config from the preinstalled Ubuntu 23.04 Server image (https://ubuntu.com/download/risc-v). I didn't make any changes to it. Interestingly... on my amd64 desktop, I only see a ssh.socket systemd service. On an rpi and my VisionFive2 I see both ssh.socket *and* ssh.service. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 fails post-installation Status in openssh package in Ubuntu: Incomplete Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020474] [NEW] openssh-server-1:9.2p1-2ubuntu1 fails post-installation
Public bug reported: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cloud-image mantic package-from-proposed riscv64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 fails post-installation Status in openssh package in Ubuntu: New Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket -
[Touch-packages] [Bug 1915792] [NEW] sudo is no longer owned by root so it no longer works
Public bug reported: sudo is no longer owned by root, so it no longer works: $ sudo dmesg sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set $ ls -l `which sudo` -rwsr-xr-x 1 2001 2501 190952 Feb 10 12:42 /usr/bin/sudo ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Tue Feb 16 09:55:07 2021 InstallationDate: Installed on 2018-07-25 (936 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RebootRequiredPkgs: gnome-shell zfs-dkms zfs-dkms SourcePackage: sudo UpgradeStatus: Upgraded to hirsute on 2020-10-31 (107 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK /etc/sudoers.d/zfs: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915792 Title: sudo is no longer owned by root so it no longer works Status in sudo package in Ubuntu: New Bug description: sudo is no longer owned by root, so it no longer works: $ sudo dmesg sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set $ ls -l `which sudo` -rwsr-xr-x 1 2001 2501 190952 Feb 10 12:42 /usr/bin/sudo ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Tue Feb 16 09:55:07 2021 InstallationDate: Installed on 2018-07-25 (936 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RebootRequiredPkgs: gnome-shell zfs-dkms zfs-dkms SourcePackage: sudo UpgradeStatus: Upgraded to hirsute on 2020-10-31 (107 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK /etc/sudoers.d/zfs: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
