-
Notifications
You must be signed in to change notification settings - Fork 37
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
Not respecting port
parameter?
#76
Comments
This seems to be the way the underlying library we use (march_hare) works: if you specify a list of hosts then the port option is ignored. However in this plugin we always pass a list, even if it's a list of 1, so the port is always ignored... We should likely just remove this port option. Currently the users can pass a list of "host" strings when the port is 5672, or "host:port" strings when the port is different than 5672. |
Ah cool! Thanks @jsvd! I didn't realise a |
There's a known issue with march_hare (ruby-amqp/march_hare#133) that causes If anyone else sees this, ignore the error message and use tcpdump to verify the traffic is going where you want. |
@jsvd Thank you so much! "host:port" is working for me now. |
I had the same problem with the RabbitMQ input plugin because I had forgotten to specify |
I'm starting up a test RabbitMQ install with:
Note that I'm using a custom port, 35007. When I start Logstash with the above configuration, it still tries to connect on port 5672:
Am I missing something?
The text was updated successfully, but these errors were encountered: