On 11/03/12 18:40, Thomas Goirand wrote:
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.
The version of rabbitmq-server in Debian (2.6.1) is slightly out of date as it lost its maintainer for a bit. The bug you reference should be fixed in 2.7.0 / 2.7.1 (deb available from http://www.rabbitmq.com/install-debian.html) due to the "rabbitmqctl stop" command not returning until the server is actually stopped.
The next release (2.8.0, imminent, by which time we should have a Debian Maintainer on the RabbitMQ team to upload it) will switch to using start-stop-daemon.
Finally, I'll look into not invoking userdel. That sounds plausible. A quick google points me to Debian bug 621833, which seems to say "do not remove".
Cheers, Simon -- Simon MacMullen RabbitMQ, VMware -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
