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

[Bryce Harrington]

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 comments in the code suggest that
under some circumstances a wait might be triggered - if you instrument
that code perhaps you can identify if it is hitting that wait, and if so
why.

Without knowing more, just switching to using 'shutdown' feels like a
kludge/workaround, and probably not what we should deploy as a fix to
this.  Instead, some additional investigation needs done to figure out
why it is delaying, or at least more specific reproduction steps so
others can do that sleuthing.

So, as I don't think there's anything more we can do on this end, I'm
going to drop the server-next tag for the time being.  Feel free to re-
add it if you think there's enough info for us to take another stab at
it though.

** Tags removed: patch server-next

-- 
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:
  rabbitmq-server does not properly shutdown

Status in rabbitmq-server package in Ubuntu:
  Incomplete

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