[PKG-Openstack-devel] Bug#812342: rabbitmq-server: Improve systemd startup scheme

Alexey Lebedeff binarin at gmail.com
Fri Jan 22 14:54:10 UTC 2016

Package: rabbitmq-server
Version: 3.5.7-1
Severity: wishlist
Tags: patch

Dear Maintainer,

Currently rabbitmq systemd unit uses `rabbitmqctl wait` as a mean to detect successful startup of
broker. But it's very fragile solution, e.g. given https://github.com/rabbitmq/rabbitmq-server/issues/463

RedHat solved this problem by using Type=notify in their systemd unit, but it required additional
erlang library `sd_notify`.

There were changes around this issue merged to rabbitmq upstream:
- https://github.com/rabbitmq/rabbitmq-server/pull/574
- https://github.com/rabbitmq/rabbitmq-server/pull/573

They will be available in RabbitMQ versions 3.6.1 and 3.7.0 and will allow to use service with
Type=notify without any extra dependencies.

So please consider applying attached patch when RabbitMQ with version greater than 3.6.1 will be

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rabbitmq-server depends on:
ii  adduser              3.113+nmu3
ii  erlang-nox           1:18.2-dfsg-2
ii  init-system-helpers  1.24
ii  logrotate            3.8.7-2

rabbitmq-server recommends no packages.

rabbitmq-server suggests no packages.

-- no debconf information

More information about the Openstack-devel mailing list