Discuss the Elastic Stack

Failed to publish events caused by: read tcp

Elastic Stack Beats

stappers (Geert Stappers) February 4, 2020, 2:16pm 2

For What Its Worth:
I do have same annoying

  logstash/async.go:256   Failed to publish events
    caused by: read tcp 192.0.2.3:59058->192.0.2.4:5044: i/o timeout

error.

In ERROR logstash/async.go:256 Failed to publish events caused by: write tcp 10.XXX.XX.XX:43522->10.XXX.XX.XX:5044: i/o timeout 2019-08-06T16:04:30.967+0800 ERROR pipeline/output.go:121 Failed to publish events:IOtimeout is it also reported (and closed after 28 days)

Pointers on what to check (journalbeat side or the logstash side) are welcome.

Topic		Replies	Views	Activity
Filebeat :- Failed to publish events caused by: client is not connected Beats filebeat	9	19563	March 19, 2020
Filebeat Error: ERR Failed to publish events caused by: read tcp i/o timeout Beats filebeat	4	14120	January 3, 2017
Filebeat log fails to publish events Beats filebeat	10	3384	March 1, 2023
Failed to publish events caused by: read tcp filebeat:33330->logstash:5044: read: connection reset by peer Beats docker , filebeat	5	2814	November 28, 2020
ERROR logstash/async.go:256 Failed to publish events caused by: write tcp 10.XXX.XX.XX:43522->10.XXX.XX.XX:5044: i/o timeout 2019-08-06T16:04:30.967+0800 ERROR pipeline/output.go:121 Failed to publish events:IOtimeout Beats filebeat	3	2121	September 9, 2019

© 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.