# Resolved: Old kibana index not working after upgrade to 6.5 (fix was to delete .kibana\_2 index)

**URL:** <https://discuss.elastic.co/t/resolved-old-kibana-index-not-working-after-upgrade-to-6-5-fix-was-to-delete-kibana-2-index/159414>\
**Category:** Kibana\
**Created:** [December 4, 2018, 7:17pm UTC](https://discuss.elastic.co/t/resolved-old-kibana-index-not-working-after-upgrade-to-6-5-fix-was-to-delete-kibana-2-index/159414 "2018-12-04T19:17:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![devops\_mike](https://avatars.discourse-cdn.com/v4/letter/d/50afbb/32.png) [@devops\_mike](https://discuss.elastic.co/u/devops_mike)\
**Post date:** [December 4, 2018, 7:17pm UTC](https://discuss.elastic.co/t/resolved-old-kibana-index-not-working-after-upgrade-to-6-5-fix-was-to-delete-kibana-2-index/159414/1 "2018-12-04T19:17:26Z")

</div>

I upgraded my ELK stack to version 6.5 today. Everything appeared to come back successfully, but upon trying to load Kibana, I just saw "Kibana server is not ready yet". Looking at my journal, I saw a message about "No shard available for [get [.kibana][doc][config:6.5.1]" within a stack trace.

I then saw Guillain's message in the thread [Kibana server is not ready yet issue after upgrade to 6.5.0](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021/4)  
He suggested using a different index, so I changed kibana.yml on the line:

```auto
kibana.index: ".kibana653"

```

While this did get Kibana running again, all our kibana work was lost, for example dashboards. Is there any way to get my old index from version 6.4 running in 6.5? I also looked at the advice under breaking changes in this article: [https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0](https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0)  
But I wasn't experiencing the permission error, at least I didn't see anything.

---

<div class="post-metadata">

**Author:** ![devops\_mike](https://avatars.discourse-cdn.com/v4/letter/d/50afbb/32.png) [@devops\_mike](https://discuss.elastic.co/u/devops_mike)\
**Post date:** [December 4, 2018, 8:46pm UTC](https://discuss.elastic.co/t/resolved-old-kibana-index-not-working-after-upgrade-to-6-5-fix-was-to-delete-kibana-2-index/159414/2 "2018-12-04T20:46:54Z")

</div>

Resolved:  
I noticed this in the Kibana logs. I was so focused on ElasticSearch logs and errors there, I somehow missed this message:

```auto
{"type":"log","@timestamp":"2018-12-04T20:36:44Z","tags":["info","migrations"],"pid":25819,"message":"Creating index .kibana_2."}
{"type":"log","@timestamp":"2018-12-04T20:36:44Z","tags":["warning","migrations"],"pid":25819,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_2 and restarting Kibana."}

```

I followed the suggestion from this and deleted .kibana\_2.

---

<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 1, 2019, 8:46pm UTC](https://discuss.elastic.co/t/resolved-old-kibana-index-not-working-after-upgrade-to-6-5-fix-was-to-delete-kibana-2-index/159414/3 "2019-01-01T20:46:57Z")

</div>

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