# Kibana server is not ready after upgrading to 7.10

**URL:** <https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029>\
**Category:** Kibana\
**Created:** [November 19, 2020, 7:24pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029 "2020-11-19T19:24:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrickr](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@patrickr](https://discuss.elastic.co/u/patrickr)\
**Post date:** [November 19, 2020, 7:24pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/1 "2020-11-19T19:24:57Z")

</div>

Hello,

We seem to constantly have issues when attempting to upgrade. This time, after the upgrade is complete and the server has rebooted, we simply get a kibana is not ready message.

Can someone provide any information on settings from 7.9 to 7.10 that would have changed and cause this issue?

Thank you,

Patrick

---

<div class="post-metadata">

**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\
**Post date:** [November 19, 2020, 7:27pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/2 "2020-11-19T19:27:13Z")

</div>

I'm not aware of any issues that prevent upgrade. What is the error you are seeing?

---

<div class="post-metadata">

**Author:** ![patrickr](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@patrickr](https://discuss.elastic.co/u/patrickr)\
**Post date:** [November 19, 2020, 7:40pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/3 "2020-11-19T19:40:31Z")

</div>

The service appears to be running correctly but I only see the message I mentioned. Usually this goes away after a few moments.

There doesn’t appear to be a log folder. Where would I see the logs for Kibana?

---

<div class="post-metadata">

**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\
**Post date:** [November 19, 2020, 7:45pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/4 "2020-11-19T19:45:21Z")

</div>

It depends on how you're running Kibana, but logs are by default sent to stdout. There will very likely be errors in the logs that will tell you what's happening.

---

<div class="post-metadata">

**Author:** ![patrickr](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@patrickr](https://discuss.elastic.co/u/patrickr)\
**Post date:** [November 19, 2020, 7:53pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/5 "2020-11-19T19:53:42Z")

</div>

I found these messages. Any idea what’s going on here?

Nov 19 11:49:24 elasticsearch kibana: {"type":"log","@timestamp":"2020-11-19T19:49:24Z","tags":["warning","savedobjects-service"],"pid":790,"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\_3 and restarting Kibana."}

Nov 19 11:49:24 elasticsearch kibana: {"type":"log","@timestamp":"2020-11-19T19:49:24Z","tags":["warning","savedobjects-service"],"pid":790,"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\_7 and restarting Kibana."}

---

<div class="post-metadata">

**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\
**Post date:** [November 19, 2020, 8:08pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/6 "2020-11-19T20:08:02Z")

</div>

Yeah, take a look at the section about [migrations](https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html)

---

<div class="post-metadata">

**Author:** ![patrickr](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@patrickr](https://discuss.elastic.co/u/patrickr)\
**Post date:** [November 19, 2020, 8:19pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/7 "2020-11-19T20:19:34Z")

</div>

I found the issue. I had to delete two indexes that appear to have been caused by the upgrade and needed to be deleted.

---

<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:** [December 17, 2020, 8:19pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-after-upgrading-to-7-10/256029/8 "2020-12-17T20:19:40Z")

</div>

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