package rabbitmq-server 1.6.0-1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

I wasnt able to reproduce this, is this still a problem?

chuck

I used 'apt-get remove --purge' and reinstalled and everything
worked fine. I wasn't paying enough attention when the problem
first occurred to provide more insightful information, but figured
the apport data might be useful, so I filed the bug. Perhaps this
bug should be marked as 'Invalid' if you can't reproduce?

On 07/30/2009 06:01 PM, Jamu Kakar wrote:
> I used 'apt-get remove --purge' and reinstalled and everything
> worked fine. I wasn't paying enough attention when the problem
> first occurred to provide more insightful information, but figured
> the apport data might be useful, so I filed the bug. Perhaps this
> bug should be marked as 'Invalid' if you can't reproduce?
>

If anyone sees this happen again please do try to post any logs you can
find. I think there may be a bug lurking about upgrades, I've heard one
other person have this happen to them but also could not reproduce.

I just ran into the same problem, please see the logs for Bug #433867.

Hmm .. here's what happens when I try "apt-get remove --purge rabbitmq-server":

{{{
Removing rabbitmq-server ...
Stopping rabbitmq-server: No nodes running
rabbitmq-server.
Purging configuration files for rabbitmq-server ...
Removing user `rabbitmq' ...
Warning: group `rabbitmq' has no more members.
userdel: user rabbitmq is currently logged in
/usr/sbin/deluser: `/usr/sbin/userdel rabbitmq' returned error code 8. Exiting.
dpkg: error processing rabbitmq-server (--purge):
 subprocess installed post-removal script returned error exit status 1
Processing triggers for sreadahead ...
Processing triggers for man-db ...
Errors were encountered while processing:
 rabbitmq-server
}}}

This is odd since rabbitmq is not even running.

Also, the laptop on which the error occurs was upgraded from jaunty. I have another laptop on which I installed karmic from scratch and rabbitmq-server installs on the latter w/o a hitch.

Right. I had compiled my own erlang system on the "problematic" machine. After removing that and installing the erlang package 'rabbitmq-server' installed fine. Sorry for any confusion caused.

The symptoms are identical to those of a bug we fixed in the RabbitMQ 1.7.0 release. Here's the relevant item from the release notes:

- prevent purging of server debian and RPM packages from failing due to epmd still running

No this hasnt been fixed.

Regards
chuck

As noted in comment #8, this bug has been fixed in the upstream 1.7.0 release. I am unsure how this should be reflected in the status.

Ok I was able to reproduce this. The init script doesnt shutdown rabbitmq-server properly I have backported the fix from 1.7.0-1 and testint it now.

Regards
chuck

This bug was fixed in the package rabbitmq-server - 1.6.0-1ubuntu1

---------------
rabbitmq-server (1.6.0-1ubuntu1) karmic; urgency=low

  * debian/init.d: Stop rabbitmq and epmd apart of fixing removing
    rabbitmq-server. (LP: #406650)
  * Update maintainer according to spec.

 -- Chuck Short <email address hidden> Mon, 19 Oct 2009 08:04:53 -0400