package lsh-server 2.0.4-dfsg-6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[oldude67]

Binary package hint: lsh-utils

was installing from synaptics.

ProblemType: Package
Architecture: i386
Date: Sun Dec 13 23:21:22 2009
DistroRelease: Ubuntu 10.04
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: lsh-server 2.0.4-dfsg-6
ProcVersionSignature: Ubuntu 2.6.32-7.10-generic-pae
SourcePackage: lsh-utils
Tags: lucid
Title: package lsh-server 2.0.4-dfsg-6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.32-7-generic-pae i686

[Magnus Holmgren (holmgren)]

Just to make sure, did you remove or disable openssh-server (sshd) or configure lsh-server to use a different port than 22?

[mikerouse (rouse-mike)]

Not for me.

[erum (vegatechx)]

Problem occur as I was installing updates through Sypnatic Package Manager

[Magnus Holmgren (holmgren)]

Once again, I would like to know the following to be able to troubleshoot the issue:
At the moment when lsh-server was installed or upgraded, was openssh-server (still) installed and running, and if so, did you configure lsh-server to use a different port from openssh-server?

If the port that lshd tries to use is taken, it will of course fail to start, which will cause package configuration to fail. That is not a bug per se, because multiple packages providing the same network service may be installed in parallel, and each generally can't be required to know about the configurations of the others. There IS a mechanism for disabling openssh-server, which admittedly has a bug, but the whole idea is actually flawed. Unfortunately there is at least one package that depends on "ssh-server" instead of "openssh-server | ssh-server", which causes lsh-server to be installed. That should still not cause lsh-server to be installed if another ssh-server package is already, so I'm interested to know exactly what the situation looked like with respect to relevant packages.

Please check /var/log/daemon.log for any lines mentioning lshd. If it says "lshd: Could not bind any address." and you are sure that no other daemon uses the same port as lsh-server, then that is interesting. To help investigate in that case, I need you to edit /etc/init.d/lsh-server and add "--debug" to both start command lines, e.g. before "--daemonic", then try to install lsh-server again or run sudo dpkg --configure --pending.

Thank you for your help!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.