Alex, thanks for looking up the Debian upstream situation, this is
looking a lot more actionable so am re-adding it to server-next.
Sounds like if we just picked the two changes to the service file from
the debian commits, those would solve the problem? If so, that should
be straightforward to
Fixes in Debian packaging which also address the problem:
-
https://salsa.debian.org/openstack-team/third-party/rabbitmq-server/commit/9764f7e6ffeaa99325b8e5ff41e80b1c4b2894d3
-
https://salsa.debian.org/openstack-team/third-party/rabbitmq-server/commit/c5b99f5c4811f460b73c8c8505a98fa55dcd752b
I'm not sure why I did not mention originally, sorry for that, but there
is a chance that what makes it reproducible is starting the daemon
inside the lxd/lxc
For those who don't use lxd - the commands would be (I don't have access
to linuxes or my infrastructure at the moment, so might be a bit
Like Christian, I also am seeing only a 1 second stop. I tried a few
different things but couldn't reproduce the delay.
I poked through /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.10/sbin
/rabbitmq-server, but it's unclear what the technical difference is
between 'stop' and 'shutdown'. Some
Hmm, the same took 1 second for me.
root@b:~# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ Messaging Server
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor
preset: enabled)
Active: inactive (dead) since Fri 2019-05-10 07:16:00 UTC; 5s
I can confirm this issue on the latest versions of 18.04.2, somewhat
nasty, really slows down reboots when RabbitMQ is installed. Here's
reproduce steps to see the bug in action:
rabbitmq installed via "sudo apt install rabbitmq-server"
Stop the service: "sudo systemctl stop
Thanks for the update Alex.
In general the package seems rather different than upstream in terms of systemd
integration.
We will have to take a wider look at this than just this line.
** Tags added: server-next
** Changed in: rabbitmq-server (Ubuntu)
Importance: Undecided => Medium
--
You
The attachment "rabbitmq-stop-shutdown.patch" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
The rabbitmq-server-release GitHub repo has a systemd file which uses
shutdown instead of stop:
https://github.com/rabbitmq/rabbitmq-server-
release/blob/master/packaging/debs/Debian/debian/rabbitmq-server.service
Switching to this will shut down rabbitmq in the expected way, instead
of having
[Expired for rabbitmq-server (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: rabbitmq-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1784757
When reporting bugs in the future please use apport by using 'ubuntu-
11 matches
Mail list logo
