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

[Christian Ehrhardt ]

Hmm, the same took 1 second for me.


root at 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 ago
  Process: 6004 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
  Process: 5348 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
 Main PID: 5348 (code=killed, signal=TERM)

May 10 07:15:40 b systemd[1]: Starting RabbitMQ Messaging Server...
May 10 07:15:41 b rabbitmq[5349]: Waiting for rabbit at b
May 10 07:15:41 b rabbitmq[5349]: pid is 5365
May 10 07:15:43 b systemd[1]: Started RabbitMQ Messaging Server.
May 10 07:15:43 b systemd[1]: rabbitmq-server.service: Failed to reset devices.list: Operation not permitted
May 10 07:15:59 b systemd[1]: Stopping RabbitMQ Messaging Server...
May 10 07:15:59 b rabbitmq[6004]: Stopping and halting node rabbit at b
May 10 07:16:00 b systemd[1]: Stopped RabbitMQ Messaging Server.


Do you have any config changes or ongoing messages running while this shutdown happens that might explain and lead us to the root cause?

The stop action is just:
  $ /usr/sbin/rabbitmqctl stop

You might change the loglevel [1] and then in a second console attach to
the log to see what is going on in that time?

[1]: https://www.rabbitmq.com/logging.html

** Changed in: rabbitmq-server (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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