Filebeat Issue - Connection Closed forcibly

Elastic Stack Beats
1

Hi All,

I have been receiving error while publishing data from filebeat to logstash.
Below is the error

2019-04-05T03:55:19.382+0530 ERROR logstash/async.go:256 Failed to publish events caused by: write tcp XX.XX.XX.XX:61346->XX.XX.XX.XX:5044: wsasend: An existing connection was forcibly closed by the remote host.

Using the same filebeat for another machine having Windows, it is working

Did telnet and the port is open and also no firewall issues

2

@Ganesh999 Logstash will close connection that are idle for too long, but the time is configurable I believe this is the issue you are gettting.

3

Hi @pierhugues thanks for the reply.The files are emitting data per second basis and that too roughly 400 events. But added ignore_older because it was reading old logs. The issue has been resolved now