[Bug 1449056] Re: rabbitmq not ready after restart

[Tony Breeds]

Trying to restate the problem a little morew clearly as after we've looked into this the 'Bug Description' is really more of a symptom.
----

The current systemd sverice definition for rabbitmq-server "completes"
before the rabbit process is actually available.  This means that
scripted environments that start rabbitmq-server and then try to talk to
it fall subject to a race (see Bug Description).

The best solution is to package erlang-sd_notify[1]  and patch rabbit
<3.5 with something like[2]  and then change the systemd service type
from 'simple' to 'notify'.  That fix is probably better for debian
unstable / wily.

For testing/vivid I propose Adding a new script that will wait for the
daemon to be available and calling that from  from the service file.

[1] https://github.com/lemenkov/erlang-sd_notify
[2] http://pkgs.fedoraproject.org/cgit/rabbitmq-server.git/tree/rabbitmq-server-0001-Add-systemd-notify-support.patch?h=f21

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

Title:
  rabbitmq not ready after restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1449056/+subscriptions