# Connection Reset By Peer **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [April 15, 2017, 3:58pm UTC](https://discuss.elastic.co/t/connection-reset-by-peer/82477 "2017-04-15T15:58:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![RAY2017](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@RAY2017](https://discuss.elastic.co/u/RAY2017)\ **Post date:** [April 15, 2017, 3:58pm UTC](https://discuss.elastic.co/t/connection-reset-by-peer/82477/1 "2017-04-15T15:58:05Z")
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 ---
**Author:** ![MarathonStudios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marathonstudios/32/17393_2.png) [@MarathonStudios](https://discuss.elastic.co/u/MarathonStudios)\ **Post date:** [April 15, 2017, 4:05pm UTC](https://discuss.elastic.co/t/connection-reset-by-peer/82477/2 "2017-04-15T16:05:49Z")
Second this. Unable to find a solution anywhere. ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [April 19, 2017, 6:01am UTC](https://discuss.elastic.co/t/connection-reset-by-peer/82477/3 "2017-04-19T06:01:00Z")
There are quite a few topics related to this on discuss: [https://discuss.elastic.co/search?q=connection%20reset%20by%20peer](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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 17, 2017, 6:10am UTC](https://discuss.elastic.co/t/connection-reset-by-peer/82477/4 "2017-05-17T06:10:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.