# Filebeat and Modules when ES Down

**URL:** <https://discuss.elastic.co/t/filebeat-and-modules-when-es-down/98410>\
**Category:** Beats\
**Created:** [August 25, 2017, 7:31pm UTC](https://discuss.elastic.co/t/filebeat-and-modules-when-es-down/98410 "2017-08-25T19:31:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ElasticChris](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@ElasticChris](https://discuss.elastic.co/u/ElasticChris)\
**Post date:** [August 25, 2017, 7:31pm UTC](https://discuss.elastic.co/t/filebeat-and-modules-when-es-down/98410/1 "2017-08-25T19:31:40Z")

</div>

Whenever I use modules like syslog or nginx, I can't get filebeat to start, if elasticsearch isn't up and running. I get:

" CRIT Exiting: Error creating ES client: Couldn't connect to any of the configured Elasticsearch host"

Is there a way to force it to start and keep trying to connect, like it would if I wasn't using modules? Or if I had logstash as my output (in which case, I'd only receive a warning). I can't count on the ES server always being up, when every client comes up.

---

<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:** [September 15, 2017, 7:31pm UTC](https://discuss.elastic.co/t/filebeat-and-modules-when-es-down/98410/2 "2017-09-15T19:31:56Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.