package likewise-open5-netlogon 5.0.3991.1+krb5-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[David A. Cobb]

Binary package hint: likewise-open5

Bah! During netinstall of karmic-beta.

Most likely caused by related bug causing LIKEWISE-OPEN5-EVENTLOG to be in a "Very Bad or Inconsistent State."

ProblemType: Package
Architecture: i386
Date: Fri Oct 9 17:45:40 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new pre-removal script returned error exit status 1
NonfreeKernelModules: nvidia
Package: likewise-open5-netlogon 5.0.3991.1+krb5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: likewise-open5
Title: package likewise-open5-netlogon 5.0.3991.1+krb5-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Uname: Linux 2.6.31-14-generic i686

[Chuck Short (zulcss)]

Hi,

I was wondering if you were still having problems.

Regards
chuck

==============

Relevant error:

Unpacking replacement likewise-open5-libs ...

Preparing to replace likewise-open5-netlogon 5.0.3991.1-0ubuntu2 (using .../likewise-open5-netlogon_5.0.3991.1+krb5-0ubuntu2_i386.deb) ...

 * Stopping Likewise Site Affinity Service 
[fail]

invoke-rc.d: initscript netlogond, action "stop" failed.

dpkg: warning: old pre-removal script returned error exit status 1

dpkg - trying script from the new package instead ...

 * Stopping Likewise Site Affinity Service 
[fail]

invoke-rc.d: initscript netlogond, action "stop" failed.

dpkg: error processing /var/cache/apt/archives/likewise-open5-netlogon_5.0.3991.1+krb5-0ubuntu2_i386.deb (--unpack):

 subprocess new pre-removal script returned error exit status 1

[Chuck Short (zulcss)]

Hi,

Thanks for the bug report, are you doing an upgrade from jaunty to karmic?

Regards
chuck

[Thierry Carrez (ttx)]

Can't reproduce on a (jaunty with likewise-open5) -> karmic upgrade.
I suspect that since you don't need likewise-open5 you disabled it somehow, that broke the upgrade (which tries to stop the daemons before upgrading), then further efforts to fix it left the package in an inconsistent state.

[David A. Cobb (superbiskit)]

  On 10/16/2009 07:59 AM, Chuck Short wrote:
> Hi,
>
> I was wondering if you were still having problems.
>
> Regards
> chuck
>
> ==============
<SNIP! />

I manually deleted the /var/lib/dpkg/info/ files related to
likewise-open5-eventlog. That convinced dpkg that there were no files
related to the package. By the time I was finished, I think the four
packages tied to this by dependency had all been re-installed. At least
there are no complaints during other installs.

--
David A. Cobb -- computing t-rex

[David A. Cobb (superbiskit)]

Re: comment #3, yes.

Re: comment #4, that sounds reasonable. I does highlight a point I tried to emphasize once or twice before. The install scripts should be rather more robust. In this case, stopping daemons should result in a post-condition "daemon(s) not running." If the script finds that the daemons are already not running, or even that they are not installed, the desired post-condition is already true. The script should exit with a "success" status.

[Thierry Carrez (ttx)]

True. Most init scripts should not [fail] when trying to stop an already-stopped service. for clarity I'll open a separate bug and make this one a duplicate of it. Thanks for bringing this to our attention !

[Alexander Torstling (atorstling)]

I got the same error (likewise-open wouldn't uninstall), but it had another cause, so I dispute the duplicate status. I got:

$ sudo apt-get remove likewise-open
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  likewise-open
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 8,069kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 299257 files and directories currently installed.)
Removing likewise-open ...
dpkg: error processing likewise-open (--remove):
 subprocess installed pre-removal script returned error exit status 1
Errors were encountered while processing:
 likewise-open
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

Manually running through the prerm script steps from /var/lib/dpkg/info/likewise-open.prerm I noticed that the following command failed:

$ sudo /usr/bin/domainjoin-cli configure --disable ssh

Error: Unable to find ssh binary [code 0x00002017]

A sshd config file was found at '/etc/ssh/sshd_config', which indicates that
sshd is installed on your system. However the sshd binary could not be found in
the search path
'/usr/sbin:/opt/ssh/sbin:/usr/local/sbin:/usr/bin:/opt/ssh/bin:/usr/local/bin:/u
sr/lib/ssh:/usr/openssh/sbin:/usr/openssh/bin:/opt/csw/sbin:/opt/csw/bin'. In
order to configure sshd, please either symlink the sshd binary into an existing
search path, or ask Likewise support to extend the search path.
$ which sshd
$

I had removed sshd, but didn't purge it, so the config was still left. Renaming /etc/ssh/sshd_config to something else made that particular command run successfully, and the prerm script ran fine. I also got the [fail] while dpkg was running the prerm-script, but that didn't cause the script to crash, so it was just a minor annoyance.