Filebeat (5.5 with modules) fails to start when ES is down

I simply copied here the same question (unanswered, auto-closed):

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, and like it does when ES goes down while filebeat is running? We have such situations often, because of running ES, Kibana and filebeats on different virtual machines, which reboot sometimes in random order...

Could you update to Filebeat 6.0 and check if you still see the same behaviour? I think we change the start logic here a bit.

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