# Unhealthy kibana instance **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-monitoring\ **Created:** [June 23, 2021, 6:20am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725 "2021-06-23T06:20:46Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ashvin\_Bhutekar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashvin_bhutekar/32/86899_2.png) [@Ashvin\_Bhutekar](https://discuss.elastic.co/u/Ashvin_Bhutekar)\ **Post date:** [June 23, 2021, 6:20am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725/1 "2021-06-23T06:20:46Z")
Unhealthy deployment, NO kibana instances are running. I am facing this issue after editing configuration in yml file. I changed edits back to the original configurations but still kibana instance is down. ---
**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:** [June 23, 2021, 8:46am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725/2 "2021-06-23T08:46:10Z")
What do your Kibana logs show? ---
**Author:** ![Ashvin\_Bhutekar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashvin_bhutekar/32/86899_2.png) [@Ashvin\_Bhutekar](https://discuss.elastic.co/u/Ashvin_Bhutekar)\ **Post date:** [June 24, 2021, 9:09am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725/3 "2021-06-24T09:09:58Z")
Received logs of nearly 100 pages and didn't find useful and exact problems in log. This is how my logs look like ![image (1)](https://us1.discourse-cdn.com/elastic/original/3X/f/6/f6dd5965d00734dd99bb513af289ec792809a104.png) ![image (2)](https://us1.discourse-cdn.com/elastic/original/3X/a/7/a73fb745c8036a4636c07ef927a5f82046848df6.png) ---
**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\ **Post date:** [June 27, 2021, 5:15am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725/4 "2021-06-27T05:15:57Z")
Hi @Ashvin_Bhutekar - I was looking at your deployment in ESS today but it seems that Kibana is not starting because of an out of memory exception. I suspect this has something to do with the saved objects migration. I see that you opened a support case - I will reply to you tomorrow in the support case. Thank you for your patience. ---
**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\ **Post date:** [June 28, 2021, 3:59am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725/5 "2021-06-28T03:59:09Z")
Hi @Ashvin_Bhutekar - I replied to your team in the support case. Your deployment is now green and available. Two reasons why Kibana was unable to start: - Given the number of saved objects in the `.kibana` index, Kibana was under-scaled and was running out of memory (OOM). - `.kibana` index contained documents from a newer Kibana version. This was preventing Kibana from starting-up (i.e saved objects migration was failing). This is a good indicator that an on-premise Kibana instance (running newer version) was connected to your ESS deployment. Such configuration is not supported. I hope that helps. If you run into any other issues with your ESS deployment, feel free to open a new support case (one of the perks from having a subscription with us 🙂 ). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 26, 2021, 3:59am UTC](https://discuss.elastic.co/t/unhealthy-kibana-instance/276725/6 "2021-07-26T03:59:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.