# ERR Harvester logs : Connection reset by peer **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [August 9, 2019, 6:45am UTC](https://discuss.elastic.co/t/err-harvester-logs-connection-reset-by-peer/194550 "2019-08-09T06:45:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![irobot678](https://avatars.discourse-cdn.com/v4/letter/i/54ee81/32.png) [@irobot678](https://discuss.elastic.co/u/irobot678)\ **Post date:** [August 9, 2019, 6:45am UTC](https://discuss.elastic.co/t/err-harvester-logs-connection-reset-by-peer/194550/1 "2019-08-09T06:45:02Z")
Hi, I am getting the following error harvester logs in kibana from filebeat and followed by info logs so , is it fine is my filebeat sending the logs after showing connection reset by peer or not ? This is happening every often , I'm getting these Err harvester logs every 1 hour or 2 hours . Do it lead to any data loss / data getting missed. Can you please help solve it. 1st Occurence: ``` 2019/08/09 01:17:47.395666 sync.go:85: ERR Failed to publish events caused by: write tcp 10.0.7.2:59538->10.3.245.189:5000: write: connection reset by peer 2019/08/09 01:17:47.395720 single.go:91: INFO Error publishing events (retrying): write tcp 10.0.7.2:59538->10.3.245.189:5000: write: connection reset by peer 2019/08/09 01:18:07.116740 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=2 libbeat.logstash.publish.read_bytes=12 libbeat.logstash.publish.write_bytes=11066 libbeat.logstash.publish.write_errors=1 libbeat.logstash.published_and_acked_events=100 libbeat.logstash.published_but_not_acked_events=100 2019/08/09 01:18:37.117289 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=2 libbeat.logstash.publish.read_bytes=18 libbeat.logstash.publish.write_bytes=21416 libbeat.logstash.published_and_acked_events=200 2019/08/09 01:19:07.117315 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=1 libbeat.logstash.publish.read_bytes=6 libbeat.logstash.publish.write_bytes=10084 libbeat.logstash.published_and_acked_events=100 2019/08/09 01:19:37.212989 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=2 libbeat.logstash.publish.read_bytes=12 libbeat.logstash.publish.write_bytes=15651 libbeat.logstash.published_and_acked_events=147 libbeat.publisher.published_events=2048 publish.events=2048 registrar.states.update=2048 registrar.writes=1 ``` 2hr later : ``` 2019/08/09 03:03:34.883488 sync.go:85: ERR Failed to publish events caused by: write tcp 10.0.6.8:51692->10.3.245.189:5000: write: connection reset by peer 2019/08/09 03:03:34.883550 single.go:91: INFO Error publishing events (retrying): write tcp 10.0.6.8:51692->10.3.245.189:5000: write: connection reset by peer 2019/08/09 03:03:47.295865 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=2 libbeat.logstash.publish.read_bytes=6 libbeat.logstash.publish.write_bytes=5407 libbeat.logstash.publish.write_errors=1 libbeat.logstash.published_and_acked_events=100 libbeat.logstash.published_but_not_acked_events=100 2019/08/09 03:04:17.295760 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=1 libbeat.logstash.publish.read_bytes=12 libbeat.logstash.publish.write_bytes=11321 libbeat.logstash.published_and_acked_events=100 2019/08/09 03:04:47.295816 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=1 libbeat.logstash.publish.read_bytes=12 libbeat.logstash.publish.write_bytes=11584 libbeat.logstash.published_and_acked_events=100 2019/08/09 03:05:17.296017 metrics.go:39: INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=1 libbeat.logstash.publish.read_bytes=6 libbeat.logstash.publish.write_bytes=9375 libbeat.logstash.published_and_acked_events=100 ``` ---
**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\ **Post date:** [August 9, 2019, 3:25pm UTC](https://discuss.elastic.co/t/err-harvester-logs-connection-reset-by-peer/194550/2 "2019-08-09T15:25:07Z")
Can you see any errors in the logs of the output? ---
**Author:** ![irobot678](https://avatars.discourse-cdn.com/v4/letter/i/54ee81/32.png) [@irobot678](https://discuss.elastic.co/u/irobot678)\ **Post date:** [August 14, 2019, 10:34am UTC](https://discuss.elastic.co/t/err-harvester-logs-connection-reset-by-peer/194550/3 "2019-08-14T10:34:11Z")
@kvch sorry for the late response. No Errors until now. I'm curious to know the reason behind these behavior. I need to know will it leads to logs missing /data loss or not ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 11, 2019, 10:34am UTC](https://discuss.elastic.co/t/err-harvester-logs-connection-reset-by-peer/194550/4 "2019-09-11T10:34:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.