# Kibana server is not ready yet, unavailable\_shards\_exception

**URL:** https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-unavailable-shards-exception/302459
**Category:** Kibana
**Created:** [April 14, 2022, 5:14pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-unavailable-shards-exception/302459 "2022-04-14T17:14:08Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Dave\_G](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@Dave\_G](https://discuss.elastic.co/u/Dave_G)
#### Post date: [April 14, 2022, 5:14pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-unavailable-shards-exception/302459/1 "2022-04-14T17:14:08Z")

</div>

We have a four-node Elasticsearch cluster running ES 7.16.2 and Kibana 7.16.2. Since the last upgrade, our Kibana page is showing

`Kibana server is not ready yet`

The Kibana log shows this error repeated numerous times:

`unavailable_shards_exception,reason:[.kibana_7.16.2_reindex_temp][0] Not enough active copies to meet shard count of [ALL] (have 1, needed 2)`

We also have 1087 unassigned Elasticsearch shards.

This cluster is set up with a single replica for shards:

```auto
"number_of_shards": "1"
"number_of_replicas": "1"
"auto_expand_replicas": "0-1"

```

A search of this error showed that it's an orchestration issue where the shutdown metadata is not cleared ([https://github.com/elastic/kibana/issues/127136](https://github.com/elastic/kibana/issues/127136)), and the recommended workaround is to delete the shutdown metadata. But doing so results in another error telling me that none of the nodes is currently shutting down:

`DELETE "_nodes/uFZB4oCySPqmp01KvTdPDw/shutdown"`

` {"error":{"root_cause":[{"type":"resource_not_found_exception","reason":"node [uFZB4oCySPqmp01KvTdPDw] is not currently shutting down"}],"type":"resource_not_found_exception","reason":"node [uFZB4oCySPqmp01KvTdPDw] is not currently shutting down"},"status":404}`

This error is repeated for each of the four nodes.

At this point I'm kind of stuck for where to go from here.

Any ideas?

---

<div class="post-metadata">

### Author: ![grfneto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grfneto/32/125776_2.png) [@grfneto](https://discuss.elastic.co/u/grfneto)
#### Post date: [April 14, 2022, 5:24pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-unavailable-shards-exception/302459/2 "2022-04-14T17:24:58Z")

</div>

Hi @Dave_G

Have you ever used the allocation explain API?  
[Cluster allocation explain API | Elasticsearch Guide [8.1] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-allocation-explain.html#cluster-allocation-explain)

Ideally, your Elasticsearch cluster is healthy enough to connect to kibana.

best regards

---

<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: [May 12, 2022, 5:25pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-unavailable-shards-exception/302459/3 "2022-05-12T17:25:00Z")

</div>

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