# Error index management Filebeat to Logstash

**URL:** <https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 11, 2020, 7:12pm UTC](https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849 "2020-02-11T19:12:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vazel](https://avatars.discourse-cdn.com/v4/letter/v/bbe5ce/32.png) [@vazel](https://discuss.elastic.co/u/vazel)\
**Post date:** [February 11, 2020, 7:12pm UTC](https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849/1 "2020-02-11T19:12:06Z")

</div>

Hi, I have the following configuration: Filebeat 7.2.0 and Logstash 7.2.0.

ERROR instance/beat.go:877 Exiting: Index management requested but the Elasticsearch output is not configured/enabled

When I run the filebeat setup -e command, I get the following error:

```
#templatsetting all commented
#output.elasticsearch
#allcommented

output.logstash
host["192.168.1.104:5044"]

setup.ilm.enabled: false 
ilm.enabled: false 

```

Reading on the network the following parameters must be set to false( setup.ilm.enabled, ilm.enabled) , but it does not work. And in other threads its resolution is not very clear, thank you

---

<div class="post-metadata">

**Author:** ![faec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faec/32/46988_2.png) [@faec](https://discuss.elastic.co/u/faec)\
**Post date:** [February 14, 2020, 5:58pm UTC](https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849/2 "2020-02-14T17:58:28Z")

</div>

I see this as well, so I've filed a bug for this issue: [https://github.com/elastic/beats/issues/16336](https://github.com/elastic/beats/issues/16336)

It seems like only a bug in the setup command, though -- when I just run `filebeat -e` instead of `filebeat setup -e` it gives no errors. If you've had any similar problems with a live Filebeat though please let us know as that would be a much more urgent bug 🙂

---

<div class="post-metadata">

**Author:** ![vazel](https://avatars.discourse-cdn.com/v4/letter/v/bbe5ce/32.png) [@vazel](https://discuss.elastic.co/u/vazel)\
**Post date:** [February 15, 2020, 7:54pm UTC](https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849/3 "2020-02-15T19:54:17Z")

</div>

Thanks very useful. Is that the """problem"". I solve the problem simply with service filebeat onestart. The problem is filebeat setup -e with this configuration (filebeat logstash)

---

<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:** [March 14, 2020, 7:54pm UTC](https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849/4 "2020-03-14T19:54:18Z")

</div>

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