Your message dated Tue, 01 May 2012 13:10:14 +0100
with message-id <[email protected]>
and subject line Re: apt-get --purge remove fails
has caused the Debian Bug report #663503,
regarding apt-get --purge remove fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
663503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663503
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rabbitmq-server
Version: 2.6.1-1
Severity: serious
Hi,
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:
rabbitmq-server*
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:
rabbitmq-server
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.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Package: rabbitmq-server
Version: 2.8.2-1
This bug was fixed in v2.8.2-1.
--- End Message ---
