package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1

Bug #1902135 reported by Dani Sojo
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openssh (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

just following the installation guide
https://community.home-assistant.io/t/installing-home-assistant-supervised-on-debian-10/200253

it crashed installing openssh-server, because docker already have the port 22 binded

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openssh-server 1:8.2p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
AptOrdering:
 ncurses-term:amd64: Install
 openssh-sftp-server:amd64: Install
 openssh-server:amd64: Install
 ssh-import-id:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Oct 29 21:04:55 2020
ErrorMessage: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2020-10-29 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd
SourcePackage: openssh
Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dani Sojo (danisojo) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
thanks for the report but IMHO there is not much to do, port 22 is SSHs port and it is right to default to it. If your local configuration has port 22 bound to something else (Docker in your case) you need to adapt the configuration of either (ssh in its half installed state or your docker/images).

There is not much the ssh (package) could do IMHO.

So this looks like a local configuration problem, rather than a bug in Ubuntu.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in openssh (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]

Changed in openssh (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.