| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes done:
- Remove the call to rabbitmq-server service inside of rabbitmq-setup
- Rewrite the rabbitmq-server service because the current
rabbitmq-server source does not support notify type of systemd unit,
the current approach does not work because the server does not run
properly the first attempt (it does if it is manually rebooted).
Fedora/devstack guys have patches to add systemd notify support
for this, see:
[1] https://peter.fedorapeople.org/rabbitmq-server-0001-Add-systemd-notify-support.patch
[2] http://pkgs.fedoraproject.org/cgit/rabbitmq-server.git/tree/rabbitmq-server-systemd-notify-support.patch
[3] http://pkgs.fedoraproject.org/cgit/rabbitmq-server.git/commit/?id=eea61e0
but this implies to add erlang-sd_notify:
[4] http://pkgs.fedoraproject.org/cgit/erlang-sd_notify.git/tree/erlang-sd_notify.spec
and [5] https://apps.fedoraproject.org/packages/erlang-sd_notify/sources/spec
and [6] possibly the erlang builder "rebar": https://github.com/rebar/rebar
- Link the rabbitmq-server service to multi.target.wants
Other interesting links to configure rabbit:
[7] https://www.rabbitmq.com/configure.html
[8] https://www.rabbitmq.com/configure.html#configuration-file
|
