# .kibana index failed **URL:** \ **Category:** Kibana\ **Created:** [October 19, 2022, 4:19am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948 "2022-10-19T04:19:48Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Harper\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harper_s1/32/103430_2.png) [@Harper\_S1](https://discuss.elastic.co/u/Harper_S1)\ **Post date:** [October 19, 2022, 4:19am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/1 "2022-10-19T04:19:48Z")
hi, could someone please advise on this. ```auto 2022-10-19T04:16:31.786+00:00][INFO][savedobjects-service] Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations... [2022-10-19T04:16:31.787+00:00][INFO][savedobjects-service] Starting saved objects migrations [2022-10-19T04:16:32.398+00:00][INFO][savedobjects-service] [.kibana_task_manager] INIT -> OUTDATED_DOCUMENTS_SEARCH_OPEN_PIT. took: 203ms. [2022-10-19T04:16:32.405+00:00][INFO][savedobjects-service] [.kibana] INIT -> OUTDATED_DOCUMENTS_SEARCH_OPEN_PIT. took: 213ms. [2022-10-19T04:16:32.484+00:00][INFO][savedobjects-service] [.kibana_task_manager] OUTDATED_DOCUMENTS_SEARCH_OPEN_PIT -> OUTDATED_DOCUMENTS_SEARCH_READ. took: 86ms. [2022-10-19T04:16:32.490+00:00][ERROR][savedobjects-service] [.kibana] Unexpected Elasticsearch ResponseError: statusCode: 500, method: POST, url: /.kibana_8.2.0_001/_pit?keep_alive=10m error: [search_phase_execution_exception]: all shards failed, [2022-10-19T04:16:32.490+00:00][FATAL][root] Error: Unable to complete saved object migrations for the [.kibana] index. Please check the health of your Elasticsearch cluster and try again. Unexpected Elasticsearch ResponseError: statusCode: 500, method: POST, url: /.kibana_8.2.0_001/_pit?keep_alive=10m error: [search_phase_execution_exception]: all shards failed, at migrationStateActionMachine (/usr/share/kibana/src/core/server/saved_objects/migrations/migrations_state_action_machine.js:164:13) at processTicksAndRejections (node:internal/process/task_queues:96:5) ``` Thanks! ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 19, 2022, 4:32am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/2 "2022-10-19T04:32:41Z")
What's the status of Elasticsearch - red/green/yellow? ---
**Author:** ![Harper\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harper_s1/32/103430_2.png) [@Harper\_S1](https://discuss.elastic.co/u/Harper_S1)\ **Post date:** [October 19, 2022, 4:35am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/3 "2022-10-19T04:35:04Z")
yellow. ---
**Author:** ![Harper\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harper_s1/32/103430_2.png) [@Harper\_S1](https://discuss.elastic.co/u/Harper_S1)\ **Post date:** [October 19, 2022, 6:52pm UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/4 "2022-10-19T18:52:17Z")
we have two data centres, one DC is up and another is down because of index failed. is there a way we can create it .kibana index and bring that DC up ? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 19, 2022, 9:34pm UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/5 "2022-10-19T21:34:17Z")
I am not sure what that means sorry. What is the output from `GET _cat/indices/.kibana?v`? ---
**Author:** ![Harper\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harper_s1/32/103430_2.png) [@Harper\_S1](https://discuss.elastic.co/u/Harper_S1)\ **Post date:** [October 20, 2022, 2:17am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/6 "2022-10-20T02:17:30Z")
```auto health status index uuid pri rep docs.count docs.deleted store.size pri.store.size yellow open .kibana_8.2.0_001 yLCqbJAGTF-VqLQl9D0mZA 1 1 549 14 2.5mb 2.5mb ``` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 20, 2022, 2:27am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/7 "2022-10-20T02:27:42Z")
Ok it's weird that it's complaining. Can you try restarting Kibana and see if it works for you? ---
**Author:** ![Harper\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harper_s1/32/103430_2.png) [@Harper\_S1](https://discuss.elastic.co/u/Harper_S1)\ **Post date:** [October 20, 2022, 2:28am UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/8 "2022-10-20T02:28:44Z")
yeah, I already did couple of time, but the same issue 😑 ---
**Author:** ![Harper\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harper_s1/32/103430_2.png) [@Harper\_S1](https://discuss.elastic.co/u/Harper_S1)\ **Post date:** [October 21, 2022, 5:56pm UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/9 "2022-10-21T17:56:42Z")
It was failing because we have two cluster, the cluster-1 has joined the cluster-2 but due to different uuid it was showing the index in yellow and kibana shard failed. Solution was to delete all the content from ~/var/lib/data-node/ and master-node from cluster-1 ( it will cause the data loss, since I had the new setup so I was okay) restart the nodes and it will join the cluster-2. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 18, 2022, 5:57pm UTC](https://discuss.elastic.co/t/kibana-index-failed/316948/10 "2022-11-18T17:57:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.