Connection Reset By Peer

Elastic Stack Beats
1

Getting connection reset by Peer when filebeat process is restarted.

2017-04-14T15:08:34-05:00 INFO Non-zero metrics in the last 30s: libbeat.logstash.published_and_acked_events=30563 filebeat.harvester.running=9 filebeat.harvester.open_files=9 filebeat.harvester.started=9 publish.events=30720 registrar.writes=15 libbeat.logstash.call_count.PublishEvents=16 libbeat.logstash.publish.read_bytes=384 libbeat.logstash.publish.write_bytes=2011120 libbeat.publisher.published_events=32605 registar.states.current=83 registrar.states.update=30720
2017-04-14T15:08:42-05:00 ERR Failed to publish events caused by: write tcp XX.XXX.XX.XXX:39736->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:08:42-05:00 INFO Error publishing events (retrying): write tcp XX.XXX.XX.XXX:39736->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:09:04-05:00 INFO Non-zero metrics in the last 30s: libbeat.publisher.published_events=36700 registrar.writes=18 libbeat.logstash.published_and_acked_events=36703 publish.events=36864 libbeat.logstash.publish.read_bytes=360 libbeat.logstash.call_count.PublishEvents=19 libbeat.logstash.publish.write_errors=1 libbeat.logstash.publish.write_bytes=2051959 libbeat.logstash.published_but_not_acked_events=2042 registrar.states.update=36864
2017-04-14T15:09:06-05:00 ERR Failed to publish events caused by: write tcp XX.XXX.XX.XXX:39984->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:09:06-05:00 INFO Error publishing events (retrying): write tcp XX.XXX.XX.XXX:39984->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:09:34-05:00 INFO Non-zero metrics in the last 30s: registrar.states.update=40960 libbeat.logstash.publish.write_bytes=2396958 libbeat.logstash.call_count.PublishEvents=21 libbeat.logstash.published_and_acked_events=40739 libbeat.logstash.published_but_not_acked_events=2036 libbeat.logstash.publish.read_bytes=354 registrar.writes=20 libbeat.publisher.published_events=40735 publish.events=40960 libbeat.logstash.publish.write_errors=1
2017-04-14T15:09:35-05:00 ERR Failed to publish events caused by: write tcp XX.XXX.XX.XXX:40212->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:09:35-05:00 INFO Error publishing events (retrying): write tcp XX.XXX.XX.XXX:40212->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:10:04-05:00 INFO Non-zero metrics in the last 30s: libbeat.logstash.publish.read_bytes=402 libbeat.logstash.published_and_acked_events=50861 registrar.writes=25 libbeat.logstash.published_but_not_acked_events=2033 libbeat.publisher.published_events=50856 publish.events=51200 libbeat.logstash.call_count.PublishEvents=26 libbeat.logstash.publish.write_bytes=2936373 libbeat.logstash.publish.write_errors=1 registrar.states.update=51200
2017-04-14T15:10:10-05:00 ERR Failed to publish events caused by: write tcp XX.XXX.XX.XXX:40338->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:10:10-05:00 INFO Error publishing events (retrying): write tcp XX.XXX.XX.XXX:40338->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:10:32-05:00 ERR Failed to publish events caused by: write tcp XX.XXX.XX.XXX:40488->YY.YYY.YY.YYY:5044: write: connection reset by peer
2017-04-14T15:10:32-05:00 INFO Error publishing events (retrying): write tcp XX.XXX.XX.XXX:40488->YY.YYY.YY.YYY:5044: write: connection reset by peer

1 Like
2

Second this. Unable to find a solution anywhere.

3

There are quite a few topics related to this on discuss: https://discuss.elastic.co/search?q=connection%20reset%20by%20peer Did you guys check the solutions there?

What did you try so far and didn't work? Please share your Filebeat version, Logstash + Logstash beats input version and how you your setup looks like.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.