Failed to connect to backoff, Filebeat on Server B and ELK on local machine

Filebeat is running on server B which read logs and pushes to ELK logstash on local Machine A.

I want to use filebeat to send real time log files from the server, and point it to my local machine where Elasticsearch, logstahs, kibana is running. But When I run Filebeat on the Server B, I get this error.

In services, I tried to see if FIlebeat started but it doesnt show up there too.

2020-01-21T16:59:59.149-0800	ERROR	pipeline/output.go:100	Failed to connect to backoff(async(tcp://192.168.40.53:5044)): dial tcp 192.168.40.53:5044: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2020-01-21T16:59:59.149-0800	INFO	pipeline/output.go:93	Attempting to reconnect to backoff(async(tcp://192.168.40.53:5044)) with 1 reconnect attempt(s)
2020-01-21T17:00:04.005-0800	INFO	[monitoring]	log/log.go:145	Non-zero metrics in the last 30s	{"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":78,"time":{"ms":78}},"total":{"ticks":406,"time":{"ms":406},"value":406},"user":{"ticks":328,"time":{"ms":328}}},"handles":{"open":206},"info":{"ephemeral_id":"0a360c35-31e5-4e4a-9a67-1e6cca6c02fa","uptime":{"ms":30186}},"memstats":{"gc_next":29718816,"memory_alloc":21262304,"memory_total":42124048,"rss":49532928},"runtime":{"goroutines":30}},"filebeat":{"events":{"active":5504,"added":5506,"done":2},"harvester":{"open_files":1,"running":1,"started":1}},"libbeat":{"config":{"module":{"running":0},"reloads":1},"output":{"type":"logstash"},"pipeline":{"clients":1,"events":{"active":4117,"filtered":1389,"published":4116,"retry":2048,"total":5506}}},"registrar":{"states":{"current":1,"update":2},"writes":{"success":2,"total":2}},"system":{"cpu":{"cores":8}}}}}
2020-01-21T17:00:22.194-0800	ERROR	pipeline/output.go:100	Failed to connect to backoff(async(tcp://192.168.40.53:5044)): dial tcp 192.168.40.53:5044: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Hi @Mehak_Bhargava,

maybe try this
https://www.elastic.co/guide/en/beats/filebeat/current/connection-problem.html#connection-problem

Fixed it. harvester wasnt reading any file because of YAML file formatting. This is working now.

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