Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tcp_listen_options is causing clients not to be able to connect #719

Closed
cabrinha opened this issue Aug 30, 2018 · 2 comments
Closed

tcp_listen_options is causing clients not to be able to connect #719

cabrinha opened this issue Aug 30, 2018 · 2 comments
Labels
docs Improvements or additions to documentation

Comments

@cabrinha
Copy link

cabrinha commented Aug 30, 2018

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.5.2
  • Ruby:
  • Distribution: CentOS 7
  • Module version: 8.2.0

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:

    {tcp_listen_options, [
         {backlog,       128},
         {nodelay,       true},
         {linger,        {true, 0}},
         {exit_on_close, false}
    ]},

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.

@wyardley
Copy link
Contributor

wyardley commented Sep 4, 2018

#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.

@wyardley wyardley added the docs Improvements or additions to documentation label Sep 4, 2018
wyardley added a commit to wyardley/puppet-rabbitmq that referenced this issue Sep 5, 2018
This adds a note in the README, and adds missing Puppet strings docs in
the main manifest.

See voxpupuli#618 and voxpupuli#621 for more details.
@wyardley
Copy link
Contributor

wyardley commented Sep 5, 2018

I've created a docs fix for this in #719 -- hope this helps.

@wyardley wyardley closed this as completed Sep 5, 2018
cegeka-jenkins pushed a commit to cegeka/puppet-rabbitmq that referenced this issue Mar 26, 2021
This adds a note in the README, and adds missing Puppet strings docs in
the main manifest.

See voxpupuli#618 and voxpupuli#621 for more details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants