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