hi all Logstash 5.4.1, filebeat 5.4.1, ubuntu, development machines (no other traffic beyond the below) I have seen a number of threads about this log message in filebeat (port 8998 is the logstash port), sometimes caused by misconfig or throttling etc. 2017/06/19 02:48:50.308090 sync.go:85: ERR …

Why does logstash send RST rather than FIN on client_inactivity_timeout

system (system) Closed July 17, 2017, 3:50am 2

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

Topic		Replies	Views
[SOLVED] TCP "RST"/reset causing Filebeat/Logstash connection reset Logstash	3	10593	May 12, 2017
Why does Logstash close idle TCP connections with RST instead of FIN? Logstash	0	71	June 9, 2025
Write connection reset by peer - Filebeat > Logstash Beats filebeat	1	1713	March 4, 2019
Logstash output traffic significantly higher than input (minimal transformations) + TCP RST Logstash	23	273	June 9, 2025
Filebeat clients unable to publish events to logstash Beats filebeat	30	437	June 3, 2025