Hi,
Using AWS elb for logstash server (3 nodes of EC2 instances), but I am getting client is unable to connect.
filebeat.log
2017-12-12T14:55:06Z ERR Failed to publish events caused by: client is not connected
2017-12-12T14:55:07Z ERR Failed to publish events: client is not connected
2017-12-12T14:55:07Z DBG connect
2017-12-12T14:55:07Z DBG 3 events out of 3 events sent to logstash. Continue sending
2017-12-12T14:55:07Z ERR Failed to publish events caused by: lumberjack protocol error
2017-12-12T14:55:07Z DBG closing
2017-12-12T14:55:07Z DBG 3 events out of 3 events sent to logstash. Continue sending
2017-12-12T14:55:07Z DBG close connection
2017-12-12T14:55:07Z DBG close connection
Filebeat is able to send logs when I write all logstash instance manually use logstash loadbalancing rather than AWS elastic loadbalancing.
hosts: ["ec2-logstash0:5043","ec2-logstash1:5043","ec2-logstash3:5043"] -- this is working with multiple instance
loadbalance : true
worker: 2
I tested with telnet logstash-elb-amazonaws.com 5043
, Able to conect.
And this with aws-elb is not working.
hosts: ["logstash-elb-amazonaws.com:5043"]
loadbalance: true --this property does not affect anything
worker: 2 -- this property also does not affect anything whether we use it or not.