# Not Getting logs due to I/O error

**URL:** <https://discuss.elastic.co/t/not-getting-logs-due-to-i-o-error/131426>\
**Category:** Logstash\
**Created:** [May 11, 2018, 7:48am UTC](https://discuss.elastic.co/t/not-getting-logs-due-to-i-o-error/131426 "2018-05-11T07:48:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [May 11, 2018, 7:48am UTC](https://discuss.elastic.co/t/not-getting-logs-due-to-i-o-error/131426/1 "2018-05-11T07:48:24Z")

</div>

Hi

I'm currently using Logstash for jboss log management.  
Configured one filebeat instance in every application server which will send logs to one logstash (for all filebeat)

Need to get logs from more than 10 jboss nodes concurrently.

**After certain time, Logs are not showing in kibana as well there is no data increase in elasticsearch.**  
**While checking logs, got below error continuously in filebeat.**

```
2018/05/11 07:47:00.865951 async.go:235: ERR Failed to publish events caused by: read tcp IP->IP: i/o timeout
2018/05/11 07:47:00.866113 async.go:235: ERR Failed to publish events caused by: read tcp IP->IP: i/o timeout

```

Also tried decrease load of logstash, So configured 2 more logstash for jboss node.  
After that also facing same issue.

_FYI, Average document count is 31242898 per day and size 15.3gb per day._  
Please suggest and help on this!

---

<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:** [June 8, 2018, 7:48am UTC](https://discuss.elastic.co/t/not-getting-logs-due-to-i-o-error/131426/2 "2018-06-08T07:48:35Z")

</div>

Closed on June 8, 2018, 7:48am UTC

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