# Exiting: resource 'filebeat-7.9.0' exists, but it is not an alias
**URL:** https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745
**Category:** Beats
**Tags:** ilm-index-lifecycle-management
**Created:** [August 20, 2020, 10:29am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745 "2020-08-20T10:29:56Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@oicfar](https://discuss.elastic.co/u/oicfar)
#### Post date: [August 20, 2020, 10:29am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/1 "2020-08-20T10:29:57Z")
hi,
after update to ELK 7.9.0 I deleted the filebeat-7.8.x indexes, templatres and now I see this
`Exiting: resource 'filebeat-7.9.0' exists, but it is not an alias`
ERROR in the log.
Regards,
Rafal
---
### Author:  [@atiwar](https://discuss.elastic.co/u/atiwar)
#### Post date: [August 24, 2020, 3:26pm UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/2 "2020-08-24T15:26:33Z")
Exiting: resource 'filebeat-7.9.0' exists, but it is not an alias
---
### Author:  [@JohanLanderholm](https://discuss.elastic.co/u/JohanLanderholm)
#### Post date: [August 25, 2020, 11:07am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/3 "2020-08-25T11:07:01Z")
I have the same situation. My filebeat has stopped working after upgrading to 7.9.0. This must be something that the qa didn't notice?
The filebeat log file also says:
Failed to connect to backoff(elasticsearch([http://172.16.0.1:9200](http://172.16.0.1:9200))): Connection marked as failed because the onConnect callback failed: resource 'filebeat-7.9.0' exists, but it is not an alias
---
### Author:  [@oicfar](https://discuss.elastic.co/u/oicfar)
#### Post date: [August 25, 2020, 11:33am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/4 "2020-08-25T11:33:15Z")
I deleted all templates and configs for filebeat-7.8.0 and filebeat-7.8.1 and added this
to my filebeat-7.9.0 index. It looks good.
By in Kibana I see often the mesage "Message now allowed". This is new after the update.
---
### Author:  [@oicfar](https://discuss.elastic.co/u/oicfar)
#### Post date: [August 25, 2020, 11:37am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/5 "2020-08-25T11:37:01Z")
I forgot to add the log entry ...
```
==> filebeat/filebeat <==
2020-08-20T01:42:41.965+0200 INFO [index-management] idxmgmt/std.go:274 ILM policy successfully loaded.
2020-08-20T01:42:41.966+0200 INFO [index-management] idxmgmt/std.go:407 Set setup.template.name to '{filebeat-7.9.0 {now/d}-000001}' as ILM is enabled.
2020-08-20T01:42:41.966+0200 INFO [index-management] idxmgmt/std.go:412 Set setup.template.pattern to 'filebeat-7.9.0-*' as ILM is enabled.
2020-08-20T01:42:41.966+0200 INFO [index-management] idxmgmt/std.go:446 Set settings.index.lifecycle.rollover_alias in template to {filebeat-7.9.0 {now/d}-000001} as ILM is enabled.
2020-08-20T01:42:41.966+0200 INFO [index-management] idxmgmt/std.go:450 Set settings.index.lifecycle.name in template to {filebeat {"policy":{"phases":{"hot":{"actions":{"rollover":{"max_age":"30d","max_size":"50gb"}}}}}}} as ILM is enabled.
2020-08-20T01:42:41.967+0200 INFO template/load.go:169 Existing template will be overwritten, as overwrite is enabled.
2020-08-20T01:42:42.689+0200 INFO template/load.go:109 Try loading template filebeat-7.9.0 to Elasticsearch
2020-08-20T01:42:42.828+0200 INFO template/load.go:101 template with name 'filebeat-7.9.0' loaded.
2020-08-20T01:42:42.828+0200 INFO [index-management] idxmgmt/std.go:298 Loaded index template.
2020-08-20T01:42:42.831+0200 ERROR instance/beat.go:951 Exiting: resource 'filebeat-7.9.0' exists, but it is not an alias
```
---
### Author:  [@tocheeba](https://discuss.elastic.co/u/tocheeba)
#### Post date: [August 25, 2020, 2:12pm UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/6 "2020-08-25T14:12:58Z")
Having the same error. Brand new 7.9.0 ELK setup. Using filebeats --\> elasticsearch for my Fortinet module.
---
### Author:  [@cripperz](https://discuss.elastic.co/u/cripperz)
#### Post date: [August 31, 2020, 4:57am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/7 "2020-08-31T04:57:26Z")
having same error on brand new filebeat setup
```auto
2020-08-31T12:54:53.612+0800 INFO template/load.go:101 template with name 'filebeat-7.9.0' loaded.
2020-08-31T12:54:53.612+0800 INFO [index-management] idxmgmt/std.go:298 Loaded index template.
2020-08-31T12:54:53.612+0800 DEBUG [esclientleg] eslegclient/connection.go:364 GET http://localhost:9200/_alias/filebeat-7.9.0
2020-08-31T12:54:53.614+0800 DEBUG [esclientleg] eslegclient/connection.go:364 HEAD http://localhost:9200/filebeat-7.9.0
2020-08-31T12:54:53.616+0800 ERROR instance/beat.go:951 Exiting: resource 'filebeat-7.9.0' exists, but it is not an alias
Exiting: resource 'filebeat-7.9.0' exists, but it is not an alias
```
---
### Author:  [@oicfar](https://discuss.elastic.co/u/oicfar)
#### Post date: [August 31, 2020, 7:02am UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/8 "2020-08-31T07:02:36Z")
I reported this as bug on GitHub.
>
>
> For confirmed bugs, please report:
> Version: 7.9.0
> Operating System: Ubuntu 20.04
> Discuss Forum URL: https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745
> Steps to Reproduce: Upgrdate or Install ELK 7.9.0
> ==\> filebeat/filebeat \<==
> 2020-08-20T01:42:41.965+0200...
---
### Author:  [@oicfar](https://discuss.elastic.co/u/oicfar)
#### Post date: [August 31, 2020, 4:10pm UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/9 "2020-08-31T16:10:28Z")
@cripperz can you post you configuration here: [https://github.com/elastic/beats/issues/20849](https://github.com/elastic/beats/issues/20849)
I can't cause I fixed my problem last week.
---
### Author:  [@Andreas\_Falk](https://discuss.elastic.co/u/Andreas_Falk)
#### Post date: [August 31, 2020, 8:17pm UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/10 "2020-08-31T20:17:37Z")
> deleted all templates and configs for filebeat-7.8.0 and filebeat-7.8.1 and added this
> 
If I may ask, where did you do that?
Is that in Kibana?
--
Regards Falk
---
### Author:  [@oicfar](https://discuss.elastic.co/u/oicfar)
#### Post date: [August 31, 2020, 8:38pm UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/11 "2020-08-31T20:38:55Z")
Yes, I did das in Kibana.
But this [Exiting: resource 'metricbeat-7.4.2' exists, but it is not an alias](https://discuss.elastic.co/t/exiting-resource-metricbeat-7-4-2-exists-but-it-is-not-an-alias/206685/3) should work too.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 28, 2020, 8:39pm UTC](https://discuss.elastic.co/t/exiting-resource-filebeat-7-9-0-exists-but-it-is-not-an-alias/245745/12 "2020-09-28T20:39:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.