This bug was fixed in the package rabbitmq-server - 3.6.10-1ubuntu0.4
---
rabbitmq-server (3.6.10-1ubuntu0.4) bionic; urgency=medium
* Improve systemd service file in order to avoid a 90-second hang
when restarting rabbitmq-server. (LP: #1784757) (Closes #902136)
-
First, verifying that the current package fails:
root@bug1784757-rabbitmq-server:~# apt policy rabbitmq-server
rabbitmq-server:
Installed: 3.6.10-1ubuntu0.3
Candidate: 3.6.10-1ubuntu0.3
Version table:
*** 3.6.10-1ubuntu0.3 500
500 http://archive.ubuntu.com/ubuntu
Hello Ivan, or anyone else affected,
Accepted rabbitmq-server into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/rabbitmq-
server/3.6.10-1ubuntu0.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Description changed:
[Impact]
- TBD
+
+ The systemd file rabbitmq-server.service on Bionic uses "Type=simple"
+ when defining the service, but unfortunately this doesn't work very well
+ for rabbitmq-server. In certain situations, systemd will fail to keep
+ track of a start/stop/restart
** Changed in: rabbitmq-server (Ubuntu Bionic)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757
Title:
[SRU] rabbitmq-server
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/rabbitmq-server/+git/rabbitmq-server/+merge/387177
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757
Title:
On Tuesday, July 07 2020, Dan Streetman wrote:
> adding @nicolasbock and @mruffell for their awareness, as rabbitmq-
> server is in x/b/f-proposed for bug 1874075 currently; hopefully that
> bug can be verified this week so it can be released at the 7-day aging
> period next monday, to clear the
adding @nicolasbock and @mruffell for their awareness, as rabbitmq-
server is in x/b/f-proposed for bug 1874075 currently; hopefully that
bug can be verified this week so it can be released at the 7-day aging
period next monday, to clear the way for this one (normally i'd suggest
just re-uploading
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/rabbitmq-server/+git/rabbitmq-server/+merge/386905
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757
Title:
I was able to reproduce this bug when using a bionic VM. I didn't have
to go through all the steps from comment #13, but I also noticed that
the bug doesn't manifest all the time; sometimes, a "systemct restart
rabbitmq-server" will take just 1 or 2 seconds. However, I was able to
reproduce the
I'm looking at this bug now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757
Title:
[SRU] rabbitmq-server does not properly shutdown
To manage notifications about this bug go to:
** Changed in: rabbitmq-server (Ubuntu Cosmic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757
Title:
[SRU] rabbitmq-server does not properly shutdown
To
# forgot to include the shutdown changes, so here's a full procedure to
fix this in Bionic:
sudo nano /lib/systemd/system/rabbitmq-server.service
# fixup the [Unit] entry to look like this:
[Unit]
Description=RabbitMQ Messaging Server
After=network.target epmd@0.0.0.0.socket
Wants=network.target
# my method to fix the problem in Bionic for now is simple, borrowing
from the upstream Debian patch:
sudo nano /lib/systemd/system/rabbitmq-server.service
# make the [Unit] definition look like this:
[Unit]
Description=RabbitMQ Messaging Server
After=network.target epmd@0.0.0.0.socket
# I run into this problem reliably in Bionic following this process, (as
of 7/19/2019, this process caused the bug to manifest)
# Clean install ubuntu server 18.04.2 (using traditional installer media, not
live media)
# (installing into a gen2 Hyper-V VM running on Windows 10 1903)
# after
I'm still not able to reproduce the error.
If you can provide an exact set of steps to run in an lxc container it'd
help a lot. Here's what I've got so far:
```
$ lxc launch ubuntu:bionic bionic-lp-1784757
Creating bionic-lp-1784757
Starting bionic-lp-1784757
** Changed in: rabbitmq-server (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757
Title:
[SRU] rabbitmq-server does not properly shutdown
To
** Bug watch added: Debian Bug tracker #812342
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812342
** Also affects: rabbitmq-server (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812342
Importance: Unknown
Status: Unknown
--
You received this bug
18 matches
Mail list logo
