# Error during metricbeat or filebeat setup

**URL:** <https://forum.opensearch.org/t/error-during-metricbeat-or-filebeat-setup/644>\
**Category:** General Feedback\
**Tags:** troubleshoot\
**Created:** [May 8, 2019, 5:05pm UTC](https://forum.opensearch.org/t/error-during-metricbeat-or-filebeat-setup/644 "2019-05-08T17:05:20Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pirolla](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pirolla/32/392_2.png) [@pirolla](https://forum.opensearch.org/u/pirolla)\
**Post date:** [October 2, 2019, 4:15pm UTC](https://forum.opensearch.org/t/error-during-metricbeat-or-filebeat-setup/644/5 "2019-10-02T16:15:58Z")

</div>

This solved it for me:

> <https://stackoverflow.com/questions/57836793/mysterious-filebeat-7-x-pack-issue-using-docker-image>

> It turns out that starting in one of the 7.x versions they turned on index lifecycle management checks by default. ILM (index lifecycle management) is an X-Pack feature, so turning this on by default means that Filebeat will do an X-Pack check by default.
> 
> This can be fixed by adding `setup.ilm.enabled: false` to the Filebeat configuration. So, not a bug per se in the OSS Docker build.

---

_[View the full topic](https://forum.opensearch.org/t/error-during-metricbeat-or-filebeat-setup/644)._