Filebeat - 127.0.0.1:5044: write: connection reset by peer


#1

For some reason, when I have logstash running locally on the same server as the beat service I get constant connection resets. There is no SSL configured and the only input. There is no firewall running. This is the current beats and logstash 5.3.

input {
beats {
port => 5044
}

And only one output:
output {
amazon_es {
hosts => ["xxx.us-east-1.es.amazonaws.com"]
region => "us-east-1"
# aws_access_key_id, aws_secret_access_key optional if instance profile is configured
aws_access_key_id => 'xxxx'
aws_secret_access_key => 'xxxx'
index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
document_type => "%{[@metadata][type]}"
}

On the same server metricbeat is successfully running connecting to the same port.


(Andrew Kroh) #2

It's probably the client_inactivity_timeout at work. Can you try increasing the value.


#3

Changing /etc/logstash/conf.d/inputs to

input {
beats {
port => 5044
client_inactivity_timeout => 240
}

Seems to alleviate the problem.


(system) #4

This topic was automatically closed after 21 days. New replies are no longer allowed.