# ERROR instance/beat.go:971 Exiting: resource 'filebeat-7.12.0' exists, but it is not an alias

**URL:** https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139
**Category:** Beats
**Tags:** ilm-index-lifecycle-management, filebeat
**Created:** [April 14, 2021, 6:57pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139 "2021-04-14T18:57:24Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![thrak](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@thrak](https://discuss.elastic.co/u/thrak)
#### Post date: [April 14, 2021, 6:57pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139/1 "2021-04-14T18:57:24Z")

</div>

Hello,

I am in the process of installing filebeats 7.12 on some elastic cluster nodes in my dev environment and when I run:

> sudo filebeat setup -e

On one of my nodes, I receive this error. ERROR instance/beat.go:971 Exiting: resource 'filebeat-7.12.0' exists, but it is not an alias

Before I ran this, I did a yum remove of filebeat, we were using an older version, and this is in our DEV environment and I just wanted a clean slate. I have done this on another node and had no issues. I followed some of the guidelines for the ILM setting such as:

> setup.ilm.enabled: true  
> setup.ilm.overwrite: true

But that threw up a different error, so I commented out those lines in the filebeat.yml file.

We are hitting a Kibana 7.8 version, not sure if that is an issue or we have to upgrade Kibana first to 7.12.

Again, I ran this same setup on another node with no issues. So my guess is now that I have moved onto the next filebeat install on the next node it is trying to overwrite and can't.

Thank you.

---

<div class="post-metadata">

### Author: ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)
#### Post date: [April 15, 2021, 8:14am UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139/2 "2021-04-15T08:14:53Z")

</div>

> [@thrak](#):
>
> On one of my nodes, I receive this error. ERROR instance/beat.go:971 Exiting: resource 'filebeat-7.12.0' exists, but it is not an alias

Did you try to remove that indice from ES before installing new filebeat?

---

<div class="post-metadata">

### Author: ![thrak](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@thrak](https://discuss.elastic.co/u/thrak)
#### Post date: [April 15, 2021, 12:04pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139/3 "2021-04-15T12:04:07Z")

</div>

> [@mtojek](#):
>
> ES b

Excuse my ignorance but how do I remove the indice from Elasticsearch? Thank you.

---

<div class="post-metadata">

### Author: ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)
#### Post date: [April 15, 2021, 12:58pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139/4 "2021-04-15T12:58:45Z")

</div>

U can do it from the index management page in kibana or use the api, [Delete index API | Elasticsearch Guide [7.12] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-delete-index.html)

---

<div class="post-metadata">

### Author: ![thrak](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@thrak](https://discuss.elastic.co/u/thrak)
#### Post date: [April 15, 2021, 2:17pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139/5 "2021-04-15T14:17:05Z")

</div>

Okay, thank you. I removed the indices. But now I am getting a completely different error.

> ERROR instance/beat.go:971 Exiting: 1 error: error loading index pattern: parsing kibana response: invalid character '\<' looking for beginning of value. Response: Elastic @font-face { font-... (truncated)  
> Exiting: 1 error: error loading index pattern: parsing kibana response: invalid character '\<' looking for beginning of value. Response: Elastic @font-face { font-... (truncated)

---

<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: [May 13, 2021, 4:17pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-971-exiting-resource-filebeat-7-12-0-exists-but-it-is-not-an-alias/270139/6 "2021-05-13T16:17:42Z")

</div>

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