[Bug 1784757] Re: [SRU] rabbitmq-server does not properly shutdown

[carl2187]

# 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 at 0.0.0.0.socket
Wants=network.target epmd at 0.0.0.0.socket

# change just the ExecStop under [Service] to use "shutdown" instead of "stop":
ExecStop=/usr/sbin/rabbitmqctl shutdown

# reload and reboot:
sudo systemctl stop rabbitmq-server.service
sudo systemctl daemon-reload
sudo systemctl restart rabbitmq-server.service
sudo shutdown -r now

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1784757

Title:
  [SRU] rabbitmq-server does not properly shutdown

Status in rabbitmq-server package in Ubuntu:
  Fix Released
Status in rabbitmq-server source package in Bionic:
  Incomplete
Status in rabbitmq-server source package in Cosmic:
  Triaged
Status in rabbitmq-server package in Debian:
  Fix Released

Bug description:
  [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

  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 at 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 at rmq-1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1784757/+subscriptions