Filebeat throws the following error message: Failed to publish events caused by: read tcp 127.0.0.1:53380->127.0.0.1:5044: i/o timeout 2020-02-03T15:45:46.987+0530 ERROR logstash/async.go:256 Failed to publish events caused by: client is not connected 2020-02-03T15:45:48.415+0530 ERROR pipeline/o…

Filebeat :- Failed to publish events caused by: client is not connected

dillip1 (dillip) February 10, 2020, 4:35pm 8

Okay. Issue is solved. I just added the client_ inactivity_timeout parameter in logstash conf file.

2 Likes

Topic		Replies	Views
Failed to publish events caused by: EOF,Failed to publish events caused by: client is not connected,Failed to publish events: client is not connected Beats filebeat	3	4769	September 18, 2019
Failed to publish events caused by: read tcp Beats filebeat	15	7568	March 11, 2020
Filebeat logs have these error messages in the log file Beats filebeat	6	1929	October 6, 2018
Filebeat Error Failed to publish events write tcp Beats filebeat	2	4466	November 20, 2019
Filebeat to logstash Logstash	1	319	March 9, 2020