# Kibana server is not ready yet

**URL:** <https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091>\
**Category:** Kibana\
**Created:** [January 25, 2021, 11:37am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091 "2021-01-25T11:37:45Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![jayanth\_m](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jayanth\_m](https://discuss.elastic.co/u/jayanth_m)\
**Post date:** [January 25, 2021, 11:37am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/1 "2021-01-25T11:37:45Z")

</div>

Im getting _ **Kibana server is not ready yet** _ error when Opening Kibana dashboard

After Looking into the logs, I observed below error:

```auto
{"type":"log","@timestamp":"2021-01-25T11:11:14Z","tags":["error","elasticsearch","data"],"pid":47885,"message":"[resource_already_exists_exception]: index [.kibana_2/Uw3DuEOERa-r67AHan80oA] already exists"}
            {"type":"log","@timestamp":"2021-01-25T11:11:14Z","tags":["warning","savedobjects-service"],"pid":47885,"message":"Unable to connect to Elasticsearch. Error: resource_already_exists_exception"}
            {"type":"log","@timestamp":"2021-01-25T11:11:14Z","tags":["warning","savedobjects-service"],"pid":47885,"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."}

```

My Question is, I have indices for past 30 days which are required for analyzing the logs.  
What if I delete .kibana\_2 and recreate will preserve the indices and logs?  
Am I be able to look after the logs after recreating .kibana\_2 indices?

Also, I observed below error whcih could be the reason for Kibana getting down

```auto
[\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"cluster_block_exception\\\",\\\"reason\\\":\\\"index](/) [.kibana_1] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];[\\\"}],\\\"type\\\":\\\"cluster_block_exception\\\",\\\"reason\\\":\\\"index](/) [.kibana_1] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];[\\\"},\\\"status\\\":429}\](/)"}"} '

```

Could can i start the Kibana again and preserve the indices and logs.

Thanks..!!

---

<div class="post-metadata">

**Author:** ![rohitarorait82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitarorait82/32/82981_2.png) [@rohitarorait82](https://discuss.elastic.co/u/rohitarorait82)\
**Post date:** [January 25, 2021, 11:42am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/2 "2021-01-25T11:42:35Z")

</div>

Hi @jayanth_m

Looks like your mount point is full , need to clear some space which also resolve your **cluster\_block\_exception**  
deleting kibana\_2 will not impact your data, it will just kill existing kibana thread

---

<div class="post-metadata">

**Author:** ![jayanth\_m](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jayanth\_m](https://discuss.elastic.co/u/jayanth_m)\
**Post date:** [January 25, 2021, 11:53am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/3 "2021-01-25T11:53:36Z")

</div>

Thanks @rohitarorait82

I've cleared the Disk space and already tried restarting the kibana, and found the issue still existed.

i've encountered the similar error last time as well and delete the .kibana\_2 index.  
unfortunately, I was not able to retrieve the old logs and indices.

So, I've posted here.

---

<div class="post-metadata">

**Author:** ![rohitarorait82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitarorait82/32/82981_2.png) [@rohitarorait82](https://discuss.elastic.co/u/rohitarorait82)\
**Post date:** [January 25, 2021, 11:57am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/4 "2021-01-25T11:57:01Z")

</div>

@jayanth_m can you please check whether elasticsearch is working or not

Also , please paste output of journalctl -xe | grep 'kibana' commanda

---

<div class="post-metadata">

**Author:** ![jayanth\_m](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jayanth\_m](https://discuss.elastic.co/u/jayanth_m)\
**Post date:** [January 25, 2021, 12:05pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/5 "2021-01-25T12:05:33Z")

</div>

Elastic search is active and running, I've just check with systemctl command.

Unfortunately, I dont have enough permission to run journalctl command on my server ☹

---

<div class="post-metadata">

**Author:** ![rohitarorait82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitarorait82/32/82981_2.png) [@rohitarorait82](https://discuss.elastic.co/u/rohitarorait82)\
**Post date:** [January 25, 2021, 12:27pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/6 "2021-01-25T12:27:53Z")

</div>

@jayanth_m : can you check whether elasticsearch is running from some time or it just getting restarted after few seconds and also have you done any upgrade recently ?

---

<div class="post-metadata">

**Author:** ![jayanth\_m](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jayanth\_m](https://discuss.elastic.co/u/jayanth_m)\
**Post date:** [January 25, 2021, 12:51pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/7 "2021-01-25T12:51:45Z")

</div>

@rohitarorait82 haven't upgraded kibana or elasticsearch recently.

w.r.t elasticsearch, after observing this issue..  
I've stopped kibana, and then elasticsearch.  
While starting, I've started elasticsearch first and started kibana after few seconds.

---

<div class="post-metadata">

**Author:** ![jayanth\_m](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jayanth\_m](https://discuss.elastic.co/u/jayanth_m)\
**Post date:** [January 26, 2021, 6:08am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/8 "2021-01-26T06:08:02Z")

</div>

@rohitarorait82

After deleting the .kibana\_2 and .kibana\_task\_manager\_2 and restarted kibana, but could find the same issue.

```auto
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["info","savedobjects-service"],"pid":21783,"message":"Creating index .kibana_task_manager_2."}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["error","elasticsearch","data"],"pid":21783,"message":"[resource_already_exists_exception]: index [.kibana_task_manager_2/c61zD_haSMKYRclSpxmccA] already exists"}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["warning","savedobjects-service"],"pid":21783,"message":"Unable to connect to Elasticsearch. Error: resource_already_exists_exception"}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["warning","savedobjects-service"],"pid":21783,"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_task_manager_2 and restarting Kibana."}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["info","savedobjects-service"],"pid":21783,"message":"Detected mapping change in \"properties.originId\""}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["info","savedobjects-service"],"pid":21783,"message":"Detected mapping change in \"properties.originId\""}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["info","savedobjects-service"],"pid":21783,"message":"Creating index .kibana_2."}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["error","elasticsearch","data"],"pid":21783,"message":"[resource_already_exists_exception]: index [.kibana_2/5GMNQUBZSFSW5URwDX8iMQ] already exists"}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["warning","savedobjects-service"],"pid":21783,"message":"Unable to connect to Elasticsearch. Error: resource_already_exists_exception"}
{"type":"log","@timestamp":"2021-01-26T06:02:32Z","tags":["warning","savedobjects-service"],"pid":21783,"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."}

```

---

<div class="post-metadata">

**Author:** ![jayanth\_m](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jayanth\_m](https://discuss.elastic.co/u/jayanth_m)\
**Post date:** [January 26, 2021, 3:09pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/9 "2021-01-26T15:09:13Z")

</div>

@rohitarorait82 I think, I've resolved this issue.

There are lot of indices(around 4 months indices) present under the elastic search.  
I have cleared all the old indices and left only with last 15 days indices.  
And then I have deleted **.kibana\_2** and **.kibana\_task\_manager\_2** and restarted kibana.  
It worked then.

Thank you 🙂

/Jayanth

---

<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:** [February 23, 2021, 3:09pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/262091/10 "2021-02-23T15:09:25Z")

</div>

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