Filebeat “connection reset by peer”


Below issue occurred while Filebeat trying to publish events to Logstash.

Failed to publish events caused by: write tcp 10.0.2.12:33822->10.2.3.17:5044: write: connection reset by peer
2017-05-06T12:55:33-05:00 INFO Error publishing events (retrying): write tcp 10.0.2.12:33822->10.2.3.17:5044: write: connection reset by peer

This can cause by many reasons :

  • Logstash is not running  or port is used by some other instance of Logstash.
  • Filebeat and Logstash versions are not compatible.
  • If fireball is enabled between different VM versions then there should be same certificate to connect with Logstash.

Integration

Complete Integration Example Filebeat, Kafka, Logstash, Elasticsearch and Kibana

Read More

To read more on Filebeat topics, sample configuration files and integration with other systems with example follow link Filebeat Tutorial  and  Filebeat Issues.

Leave you feedback to enhance more on this topic so that make it more helpful for others.

 

About Saurabh Gupta

My Name is Saurabh Gupta, I have approx. 10 Year of experience in Information Technology World manly in Java/J2EE. During this time I have worked with multiple organization with different client, so many technology, frameworks etc.
This entry was posted in Filebeat Issues and tagged , . Bookmark the permalink.