# Index .kibana\_1 already exists during startup(7.7.0)

**URL:** <https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549>\
**Category:** Kibana\
**Created:** [December 14, 2020, 8:34am UTC](https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549 "2020-12-14T08:34:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zj27](https://avatars.discourse-cdn.com/v4/letter/z/b4bc9f/32.png) [@zj27](https://discuss.elastic.co/u/zj27)\
**Post date:** [December 14, 2020, 8:34am UTC](https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549/1 "2020-12-14T08:34:18Z")

</div>

Hi when I first start the Kibana on a clean environment, sometimes it will fail with error "Index .kibana\_1 already exists ". I checked the log and code, then noticed the the .kibana\_1 was created but took too long time to response, so that I think Kibana though it's timeout. Because the .kibana\_1 hasn't been aliased to .kibana, so next time it will still retry the index creation but failed. Is that a known issue?

---

<div class="post-metadata">

**Author:** ![majagrubic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majagrubic/32/74459_2.png) [@majagrubic](https://discuss.elastic.co/u/majagrubic)\
**Post date:** [December 14, 2020, 11:33am UTC](https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549/2 "2020-12-14T11:33:52Z")

</div>

This is a known issue once a saved object migration fails for some. We had been working on [fixing](https://github.com/elastic/kibana/issues/52202) this. You can manually delete `.kibana_1` index and a new one will be created the next time Kibana starts.

---

<div class="post-metadata">

**Author:** ![zj27](https://avatars.discourse-cdn.com/v4/letter/z/b4bc9f/32.png) [@zj27](https://discuss.elastic.co/u/zj27)\
**Post date:** [December 16, 2020, 2:58am UTC](https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549/3 "2020-12-16T02:58:44Z")

</div>

Thank you Maja. In my case I didn't perform any actual migration yet as it's a new env, but I suppose it should be same issue no matter the migration happened or not, right? BTW, may I know which version the problem had been fixed, 8.0.0 or 7.11.0?

---

<div class="post-metadata">

**Author:** ![majagrubic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majagrubic/32/74459_2.png) [@majagrubic](https://discuss.elastic.co/u/majagrubic)\
**Post date:** [December 16, 2020, 8:30am UTC](https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549/4 "2020-12-16T08:30:56Z")

</div>

Neither 8.0.0 nor 7.11 versions are out yet 🙂 Going with the latest version - currently 7.10 - is always your safest bet.

---

<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:** [January 13, 2021, 8:31am UTC](https://discuss.elastic.co/t/index-kibana-1-already-exists-during-startup-7-7-0/258549/5 "2021-01-13T08:31:09Z")

</div>

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