You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having these options in the config makes clients fail to connect. Removing these lines from the config, clients can connect fine. Please add an option to be able to remove these lines from the config as these seem to not be sane defaults.
setting config_ranch => false seems to have solved my issue, please update the readme to explain this option.
The text was updated successfully, but these errors were encountered:
#621 has some more background and discussion about this
If memory serves, we intended to avoid making the behavior too "magical" (and keep it idempotent) by basing it on the rabbitmq version fact.
If I get a chance, I'll add a note somewhere in the README and also document that param in the docstrings.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
use this module
What are you seeing
Clients aren't connecting
What behaviour did you expect instead
i expect clients to be able to connect
Output log
[E 180830 21:31:31 events:123] Failed to capture events: '[Errno 104] Connection reset by peer', trying again in 4 seconds.
Any additional information you'd like to impart
There should be an option to not include this part of the config:
Having these options in the config makes clients fail to connect. Removing these lines from the config, clients can connect fine. Please add an option to be able to remove these lines from the config as these seem to not be sane defaults.
setting
config_ranch => false
seems to have solved my issue, please update the readme to explain this option.The text was updated successfully, but these errors were encountered: