ansible-rabbitmq
ansible-rabbitmq copied to clipboard
[MAINTAINER NEEDED] Ansible role configuring RabbitMQ cluster
Hello, guys. This role is quite useful and somewhat popular, but it has a lot of bugs and a lot of space to improve. It was used to spin up...
Related issue: https://github.com/rabbitmq/rabbitmq-server/issues/832
initscript of the rabbitmq-server is complaining about the whitespace for `RABBITMQ_NODE_PORT` ```sh root@node:~# cat /etc/default/rabbitmq-server # This file is sourced by /etc/init.d/rabbitmq-server. Its primary # reason for existing is to...
…its init-Script: /etc/init.d/rabbitmq-server start /etc/init.d/rabbitmq-server: 12: /etc/default/rabbitmq-server: 25672: not found
Adds the force: yes option to the command adding RabbitMQ users. Fixes issue where users' passwords where not being changed after setting for the first time. Fixes alexey-medvedchikov/ansible-rabbitmq#42 Signed-off-by: Jason...
Noticed that users maintain the original password even when their password is changed in the `rabbitmq_users` var. Fixed it by adding the `force: yes` option here: https://github.com/alexey-medvedchikov/ansible-rabbitmq/blob/98a4ee35d0725c462b4a8f23c19a0171d8dbbf89/tasks/rabbitmq.yml#L17
RABBITMQ_NODE_PORT= {{ rabbitmq_node_port }} should be RABBITMQ_NODE_PORT={{ rabbitmq_node_port }} please consider to update it, thanks.
[all] hosts: - { ip: '10.0.0.1', domain: 'mq1' } - { ip: '10.0.0.2', domain: 'mq2' } - { ip: '10.0.0.3', domain: 'mq3' } - { ip: '10.0.0.4', domain: 'mq4' }
Based on PR #8, but without misc other changes In our Amazon production cloud we want to install specific versions of RabbitMQ that have been tested and validated to work...