# Failed to publish events caused by: read tcp

**URL:** <https://discuss.elastic.co/t/failed-to-publish-events-caused-by-read-tcp/217410>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 31, 2020, 3:13pm UTC](https://discuss.elastic.co/t/failed-to-publish-events-caused-by-read-tcp/217410 "2020-01-31T15:13:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stappers](https://avatars.discourse-cdn.com/v4/letter/s/df705f/32.png) [@stappers](https://discuss.elastic.co/u/stappers)\
**Post date:** [February 4, 2020, 2:16pm UTC](https://discuss.elastic.co/t/failed-to-publish-events-caused-by-read-tcp/217410/2 "2020-02-04T14:16:21Z")

</div>

For What Its Worth:  
I do have same annoying

```auto
  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](https://discuss.elastic.co/t/error-logstash-async-go-256-failed-to-publish-events-caused-by-write-tcp-10-xxx-xx-xx-43522-10-xxx-xx-xx-i-o-timeout-2019-08-06t1630-967-0800-error-pipeline-output-go-121-failed-to-publish-events-iotimeout/194355) is it also reported (and closed after 28 days)

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

---

_[View the full topic](https://discuss.elastic.co/t/failed-to-publish-events-caused-by-read-tcp/217410)._