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 SRU.
** Tags added: server-next
** Changed in: rabbitmq-server (Ubuntu)
Status: Incomplete => Triaged
** Also affects: rabbitmq-server (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: rabbitmq-server (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
- When I run `systemctl restart rabbitmq-server` it waits for 90 seconds
- then systemd sends SIGKILL to it.
+ [Impact]
+ TBD
+
+ [Test Case]
+ TBD
+
+ [Regression Potential]
+ TBD
+
+ [Fix]
+ TBD
+
+ The fix is available upstream in Debian as of 3.7.6, so would need
+ backported for bionic and cosmic:
+
+ rabbitmq-server | 3.5.7-1 | xenial | source, all
+ rabbitmq-server | 3.6.10-1 | bionic | source, all
+ rabbitmq-server | 3.6.10-1 | cosmic | source, all
+ rabbitmq-server | 3.7.8-4ubuntu2 | disco | source, all
+ rabbitmq-server | 3.7.8-4ubuntu2 | eoan | source, all
+
+ [Discussion]
+ TBD
+
+ [Original Report]
+ When I run `systemctl restart rabbitmq-server` it waits for 90 seconds then
systemd sends SIGKILL to it.
Presumably the `epmd` process does not receive SIGTERM, since if I run
`kill 1493` (or whatever pid it currently is) then restart happens
straight after that successfully
● rabbitmq-server.service - RabbitMQ Messaging Server
- Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled;
vendor preset: enabled)
- Active: deactivating (final-sigterm) since Wed 2018-08-01 01:17:04 UTC; 7s
ago
- Process: 1183 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited,
status=0/SUCCESS)
- Process: 178 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait
(code=exited, status=0/SUCCESS)
- Process: 177 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
- Main PID: 177 (code=killed, signal=TERM)
- Tasks: 1 (limit: 4915)
- CGroup: /system.slice/rabbitmq-server.service
- └─1493 /usr/lib/erlang/erts-9.2/bin/epmd -daemon
+ Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled;
vendor preset: enabled)
+ Active: deactivating (final-sigterm) since Wed 2018-08-01 01:17:04 UTC; 7s
ago
+ Process: 1183 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited,
status=0/SUCCESS)
+ Process: 178 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait
(code=exited, status=0/SUCCESS)
+ Process: 177 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
+ Main PID: 177 (code=killed, signal=TERM)
+ Tasks: 1 (limit: 4915)
+ CGroup: /system.slice/rabbitmq-server.service
+ └─1493 /usr/lib/erlang/erts-9.2/bin/epmd -daemon
Aug 01 01:11:20 rmq-1 systemd[1]: rabbitmq-server.service: Failed to reset
devices.list: Operation not permitted
Aug 01 01:11:20 rmq-1 systemd[1]: Starting RabbitMQ Messaging Server...
Aug 01 01:11:25 rmq-1 rabbitmq[178]: Waiting for 'rabbit@rmq-1'
Aug 01 01:11:25 rmq-1 rabbitmq[178]: pid is 204
Aug 01 01:11:30 rmq-1 systemd[1]: Started RabbitMQ Messaging Server.
Aug 01 01:17:04 rmq-1 systemd[1]: Stopping RabbitMQ Messaging Server...
Aug 01 01:17:06 rmq-1 rabbitmq[1183]: Stopping and halting node 'rabbit@rmq-1'
** Changed in: rabbitmq-server (Ubuntu Bionic)
Status: New => Triaged
** Changed in: rabbitmq-server (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: rabbitmq-server (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: rabbitmq-server (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: rabbitmq-server (Ubuntu)
Status: Triaged => Fix Released
** Summary changed:
- rabbitmq-server does not properly shutdown
+ [SRU] rabbitmq-server does not properly shutdown
--
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:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1784757/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
