# Filebeat - Failed to publish events caused by: read tcp x.x.x.x:36196-\>x.x.x.x:5045: i/o timeout

**URL:** <https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-read-tcp-x-x-x-x-36196-x-x-x-x-5045-i-o-timeout/128994>\
**Category:** Logstash\
**Created:** [April 22, 2018, 9:08am UTC](https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-read-tcp-x-x-x-x-36196-x-x-x-x-5045-i-o-timeout/128994 "2018-04-22T09:08:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomer\_Lev1](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@Tomer\_Lev1](https://discuss.elastic.co/u/Tomer_Lev1)\
**Post date:** [April 22, 2018, 9:08am UTC](https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-read-tcp-x-x-x-x-36196-x-x-x-x-5045-i-o-timeout/128994/1 "2018-04-22T09:08:46Z")

</div>

Hi i'm running into a problem while sending logs via filebeat to logstash:  
In short - Can't see logs in kibana - when tailing the filebeat log I see a lot of these:  
ERROR logstash/async.go:235 Failed to publish events caused by: read tcp x.x.x.x:36246-\>y.y,y.y:5045: i/o timeout (while y.y,y.y is logstash address and 5045 is the open beat port)

More details:  
I have ~60 machines with filebeat 6.1.1 installed and one logstash machine with logstash 6.2.3 installed.  
Some filebeats successfully sends their logs while some throws the error I mentioned above.  
those non-errors filebeats sends old logs - means I can see in logstash debug logs that some logs timestamp are 2 or 3 days ago

Logstash usage memory is 35% and cpu usage near 75% on peaks,  
in netstat -tupn output in the filebeat machines I can see that the established connections to logstash from filebeat.

Can someone help me find the problem ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 20, 2018, 9:08am UTC](https://discuss.elastic.co/t/filebeat-failed-to-publish-events-caused-by-read-tcp-x-x-x-x-36196-x-x-x-x-5045-i-o-timeout/128994/2 "2018-05-20T09:08:51Z")

</div>

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