Failed to publish events caused by: write tcp X.X.X.X:36524->X.X.X.X:5044: write: connection reset by peer error in filebeat

[Aqel]

I am getting this error while trying to push logs using filebeat to logstash.

|filebeat       | 2020-06-14T16:45:36.660318702Z 2020-06-14T16:45:36.660Z|ERROR|logstash/async.go:256|Failed to publish events caused by: write tcp X.X.X.X:36524->X.X.X.X:5044: write: connection reset by peer|
|---|---|---|---|
|filebeat       | 2020-06-14T16:45:38.013422207Z 2020-06-14T16:45:38.012Z|ERROR|pipeline/output.go:121|Failed to publish events: write tcp X.X.X.X:36524->X.X.X.X:5044: write: connection reset by peer|
|filebeat       | 2020-06-14T16:45:38.013457133Z 2020-06-14T16:45:38.012Z|INFO|pipeline/output.go:95|Connecting to backoff(async(tcp://xx.xx:5044))|

Can someone please help me ?

My logstash pipelines

02-beats-input.conf

input {
  beats {
    port => 5044
  }
}

10-syslog-filter.conf

filter {
    json {
    	source => "message"
    }
}

30-elasticsearch-output.conf

output {
  elasticsearch {
    hosts => ["localhost:9200"]
    manage_template => false
    index => "index-%{+YYYY.MM.dd}"
  }
}

When I do telnet xx.xx 5044, this is the what I see in terminal

Trying X.X.X.X...
Connected to ace.elastic.
Escape character is '^]'

NOTE : This configuration used to work before and I have not changed anything related to logstash or filebeat.

[Coinology (Joshua Jones)]

@Aqel Welcome to the community!

It'd be helpful to see your Filebeat config / Logstash pipeline. Also, please use the formatting features here on the forum when posting logs / code (the </> button or you can use pairs of `).

[Aqel]

@Coinology Thanks for the comment. I have formatted the description and added the logstash pipelines.