Filebeat +Logstash write: connection reset by peer（已解决）

2020/05/26

记一次FIlebeat 异常，目前没有深究解决方案，不影响使用。

2020/05/28  今天抽出时间去排查这个问题。

首先不确定对每个人都受用，但是在我这边是可以解决。

connection reset by peer：我这边是因为搭了个测试环境操作不频繁导致Logstash可能由于不工作而尝试重置连接，在这种情况下应该会引起connection reset by peer。你可以尝试在可以尝试在Logstash配置文件中添加client_inactivity_timeout这个参数就可以解决下面附上我的配置：

 

input{
    betas{
        port =>5044
        client_inactivity_timeout => 36000
     }
}

参考：https://discuss.elastic.co/t/solved-filebeat-logstash-connection-reset-by-peer/87012

2020/05/26 06:48:35.384662 metrics.go:34: INFO No non-zero metrics in the last 30s
2020/05/26 06:49:05.384659 metrics.go:34: INFO No non-zero metrics in the last 30s
2020/05/26 06:49:35.384751 metrics.go:34: INFO No non-zero metrics in the last 30s
2020/05/26 06:49:35.436374 log.go:91: INFO Harvester started for file: /opt/apache-tomcat-8.5.6-log-8089/logs/ds-logservice-web/error-s.log
2020/05/26 06:49:40.408966 sync.go:85: ERR Failed to publish events caused by: write tcp 192.168.2.63:57732->192.168.2.61:5044: write: connection reset by peer
2020/05/26 06:49:40.409005 single.go:91: INFO Error publishing events (retrying): write tcp 192.168.2.63:57732->192.168.2.61:5044: write: connection reset by peer
2020/05/26 06:50:05.384693 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.logstash.call_count.PublishEvents=3 libbeat.logstash.publish.read_bytes=18 libbeat.logstash.publish.write_bytes=1267 libbeat.logstash.publish.write_errors=1 libbeat.logstash.published_and_acked_events=4 libbeat.logstash.published_but_not_acked_events=3 libbeat.publisher.published_events=4 publish.events=6 registrar.states.cleanup=1 registrar.states.update=6 registrar.writes=3