Discuss the Elastic Stack

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

Elastic Stack Beats

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	Activity
Filebeat error failed to publish events caused connection reset by peer Beats filebeat	6	9943	April 27, 2021
URGENT: ERR Failed to publish events caused by: write tcp [::1]:60383->[::1]:5044: wsasend: An established connection was aborted by the software in your host machine Beats	5	3298	July 6, 2017
"Failed to publish events", "use of closed network connection" Beats filebeat	13	10394	April 19, 2018
ERR Failed to publish events caused by: read tcp 127.0.0.1:50248->127.0.0.1:5601: i/o timeout Beats winlogbeat	14	6262	October 24, 2017
Updating to version 7.17.15 caused the 'Failed to publish events' issue caused connection reset by peer Elasticsearch elastic-stack-monitoring	1	168	January 3, 2024

© 2020. All Rights Reserved - Elasticsearch

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.