# FileBeat EOF Error

**URL:** <https://discuss.elastic.co/t/filebeat-eof-error/60882>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 19, 2016, 12:38pm UTC](https://discuss.elastic.co/t/filebeat-eof-error/60882 "2016-09-19T12:38:56Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![il.bert](https://avatars.discourse-cdn.com/v4/letter/i/ac91a4/32.png) [@il.bert](https://discuss.elastic.co/u/il.bert)\
**Post date:** [October 7, 2016, 9:54am UTC](https://discuss.elastic.co/t/filebeat-eof-error/60882/25 "2016-10-07T09:54:19Z")

</div>

Hi, sadly our test did not proceed well, none of the above workaround worked 100%, we were still getting that error.  
As we had the opportunity, we moved to a larger cluster: 3 HUGE machines. We expected one of them to be able to take the whole load but we used 3 for test.

It happened again. EOF

Thus it could not be a problem of fully loaded machine so we moved to changing other parameters.  
We found out that removing `load_balance` in filebeat solved the problem, or at least it seems to.

Again using only 1 single logstash output in filebeat works good (we split our source in 3 group and each group goes to one LS machine), now we have this configuration from 24h and it's working pretty well.

This is not a good solution for us, as we have a cluster of machines we wants it to be working efficiently and reliably.  
Do you have any idea on why this is happening? how may we solve it?

thanks

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-eof-error/60882)._