I'm sorry that it's the 2nd time today that I have to send a RC bug
against this package... :(
This one is very easy to reproduce. Luckily, it's also very easy to fix!
Why are you even trying to userdel rabbitmq? Just don't do that, it's
really ok (and I believe *better*) to leave the system user when the
package is removed. Anyway, the issue is very simple: you are deleting
the user *before* rabbitmq had enough time to shutdown. That's in fact
one more reason why you should be using start-stop-daemon, in your init.d
script, which will wait nicely until the daemon dies.
Anyway, here's how to reproduce. Install a fresh SID, then do:
apt-get install rabbitmq-server
Then try to remove:
apt-get --purge remove rabbitmq-server
Then here's the error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 1,970 kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 22278 files and directories currently installed.)
Removing rabbitmq-server ...
Stopping rabbitmq-server: rabbitmq-server.
Purging configuration files for rabbitmq-server ...
Removing user `rabbitmq' ...
Warning: group `rabbitmq' has no more members.
userdel: user rabbitmq is currently used by process 1771
/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 man-db ...
configured to not write apport reports
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
Of course, if you do that a 2nd time, since the daemon is already stopped,
it will work.
Thomas Goirand (zigo)
To UNSUBSCRIBE, email to debian-bugs-rc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com