# How to resolve Dangling indices error on each Index

**URL:** https://discuss.elastic.co/t/how-to-resolve-dangling-indices-error-on-each-index/130609
**Category:** Elasticsearch
**Created:** [May 4, 2018, 10:53am UTC](https://discuss.elastic.co/t/how-to-resolve-dangling-indices-error-on-each-index/130609 "2018-05-04T10:53:17Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)
#### Post date: [May 9, 2018, 9:56am UTC](https://discuss.elastic.co/t/how-to-resolve-dangling-indices-error-on-each-index/130609/11 "2018-05-09T09:56:11Z")

</div>

Your index listing is not including the `.kibana` index at all, which doesn't explains why it can't be imported. Did you manually delete this index before get the listing?

Also all indices are in `red` state, so there are some serious issues going on with this node that is preventing the cluster to get to a working state so Kibana can work too.

I suggest that you:

1. Stop the node.
2. For every `uuid` in that index listing, move away the directory, with the same `uuid` name, from outside directory (under Elasticsearch data path) `nodes/0/indices`.
3. Start the node and verifies if Kibana can connect to it

---

_[View the full topic](https://discuss.elastic.co/t/how-to-resolve-dangling-indices-error-on-each-index/130609)._
