package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd

[Ton]

openssh-server is installed, but cannot be reinstalled

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ssh 1:7.2p2-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 libgraphite2-3: Install
 openssh-server: Configure
 ssh: Configure
 libgraphite2-3: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Aug 22 10:13:58 2017
ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
InstallationDate: Installed on 2014-04-20 (1221 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: openssh
Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
UpgradeStatus: No upgrade log present (probably fresh install)

[Christian Ehrhardt  (paelzer)]

Hi,
from your log:
aug 23 09:45:31 hostname sshd[1051]: error: Bind to port 22 on 192.168.2.4 failed: Cannot assign requested address.
aug 23 09:45:31 hostname sshd[1051]: fatal: Cannot bind any address.
aug 23 09:45:31 hostname systemd[1]: Failed to start OpenBSD Secure Shell server.

It seems you have configured a listen address that does not exist.
This makes the server (re-)start fail.

And that in turn will break updates/installs.

Please fix your configuration of sshd and things will resolve.

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or 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.

[Launchpad Janitor (janitor)]

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