Filebeat :- Failed to publish events caused by: client is not connected

[dillip1 (dillip)]

Okay. Issue is solved. I just added the client_ inactivity_timeout parameter in logstash conf file.

[SOLVED] TCP "RST"/reset causing Filebeat/Logstash connection reset

I'm embarrassed it took me so long to solve this. Turns out all I needed to do was specify a client_inactivity_timeout of more than the default of 60 seconds. In my particular situation the client (on a test server) was relatively inactive, causing Logstash to kill the connection after 60 seconds. Increasing this beyond the inactivity time resolved the issue. input { beats { client_inactivity_timeout => 1200 port => 5044 } } Thanks, Greg