# Beat dont' ship log to ES when ES restart (ES died)

**URL:** <https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189>\
**Category:** Beats\
**Created:** [March 2, 2016, 3:41am UTC](https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189 "2016-03-02T03:41:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [March 2, 2016, 3:41am UTC](https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189/1 "2016-03-02T03:41:21Z")

</div>

I'm using ES 2.0.

My cluster is full storage \>85% (Status Red). i try to Remove some indices and restart cluster, status healthy is green. But filebeat and winlogbeat installed in server don't ship log to LS and ES. I must try to restart server filebeat and winlogbeat in server. It's working !

Please tell me why ☹

Thanks !

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 2, 2016, 5:41am UTC](https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189/2 "2016-03-02T05:41:59Z")

</div>

Beats stop when they cannot connect to ES, but they should restart when things are ok.

What version are you using?

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [March 2, 2016, 11:40pm UTC](https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189/3 "2016-03-02T23:40:17Z")

</div>

I'm ussing filebeat version 1.01. Logstash version 2.1

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [March 3, 2016, 12:16am UTC](https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189/4 "2016-03-03T00:16:02Z")

</div>

I guess you're having some error logs in logstash/filebeat and at some time filebeat eventually stops shipping logs.

Update to filebeat version 1.1.1 ! This release contains a bug fix for output potentially hanging in error recovery.

---

<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:** [July 5, 2017, 9:55pm UTC](https://discuss.elastic.co/t/beat-dont-ship-log-to-es-when-es-restart-es-died/43189/5 "2017-07-05T21:55:08Z")

</div>