# Logstash after upgrade to 5.6.3 from 2.1.3, ES output module: continues to do health checking

**URL:** <https://discuss.elastic.co/t/logstash-after-upgrade-to-5-6-3-from-2-1-3-es-output-module-continues-to-do-health-checking/106484>\
**Category:** Logstash\
**Created:** [November 6, 2017, 8:29am UTC](https://discuss.elastic.co/t/logstash-after-upgrade-to-5-6-3-from-2-1-3-es-output-module-continues-to-do-health-checking/106484 "2017-11-06T08:29:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [November 6, 2017, 1:20pm UTC](https://discuss.elastic.co/t/logstash-after-upgrade-to-5-6-3-from-2-1-3-es-output-module-continues-to-do-health-checking/106484/2 "2017-11-06T13:20:15Z")

</div>

Turned out there still were some 'breaking changes' issues in some ruby filter code  
See also [Logstash.agent - Error in reactor loop escaped: Bad file descriptor](https://discuss.elastic.co/t/logstash-agent-error-in-reactor-loop-escaped-bad-file-descriptor/106519/1)

---

_[View the full topic](https://discuss.elastic.co/t/logstash-after-upgrade-to-5-6-3-from-2-1-3-es-output-module-continues-to-do-health-checking/106484)._