# ILM Error **URL:** https://discuss.elastic.co/t/ilm-error/192773 **Category:** Kibana **Created:** [July 29, 2019, 8:24pm UTC](https://discuss.elastic.co/t/ilm-error/192773 "2019-07-29T20:24:38Z") **Posts on this page:** 1 **Showing post:** 12
### Author: ![Stef\_Nestor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stef_nestor/32/85483_2.png) [@Stef\_Nestor](https://discuss.elastic.co/u/Stef_Nestor) #### Post date: [August 3, 2021, 11:22pm UTC](https://discuss.elastic.co/t/ilm-error/192773/12 "2021-08-03T23:22:50Z")
Thanks in a large part to this lovely post, we now cover these and other top ILM configuration errors on our [Troubleshooting ILM](https://www.elastic.co/blog/troubleshooting-elasticsearch-ilm-common-issues-and-fixes) blog. Direct summarized resolutions: > **`index.lifecycle.rollover_alias [x] does not point to index [y]`** > > You’ll need to check your [index settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-settings.html) `index.lifecycle.rollover_alias` . Either the index is pointing to the wrong alias or the alias does not exist. You can check the latter by running [Get Aliases](https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-alias.html). Here’s an example [Elastic Discuss issue](https://discuss.elastic.co/t/index-lifecycle-error/171254). You may consider [Data Streams](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams.html) which handle this for you. > **`alias [x] has more than one write index [y,z]`** > > When you run [Get Aliases](https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-alias.html), you’ll notice that two indices are marked as `is_write_index:true` when only one should be per alias. You’ll want to toggle `is_write_index:false` on one of the indices via the [Aliases API](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html). --- _[View the full topic](https://discuss.elastic.co/t/ilm-error/192773)._