# Upgraded from 6.4.2 to 6.5.0. Says "Kibana server is not ready yet" **URL:** \ **Category:** Kibana\ **Created:** [November 16, 2018, 7:34am UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994 "2018-11-16T07:34:20Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![mlemartien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mlemartien/32/30958_2.png) [@mlemartien](https://discuss.elastic.co/u/mlemartien)\ **Post date:** [November 16, 2018, 7:34am UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/1 "2018-11-16T07:34:20Z")
Hi did my rolling upgrade this morning: Logstahs, then Elastic then Kibana. Everything went well and cluster (3 nodes) status is green. Now when starting Kibana, it says in the browser: _Kibana server is not ready yet_ It's been doing that for 1/2 hour now. Looking at the logs I see: _nov. 16 06:57:24 uatelastic\_client1 kibana[2077]: {"type":"log","@timestamp":"2018-11-16T06:57:24Z","tags":["warning","migrations"],"pid":2077,"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."}_ I did exactly what is suggested but it did not help. Same problem remains. I tried a second time and then had the same issue with index .kibana\_1. Any thoughts? ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [November 16, 2018, 4:33pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/2 "2018-11-16T16:33:53Z")
According to the message you will need to remove `.kibana_2` as well. ---
**Author:** ![fracklen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fracklen/32/32630_2.png) [@fracklen](https://discuss.elastic.co/u/fracklen)\ **Post date:** [November 19, 2018, 8:41am UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/3 "2018-11-19T08:41:41Z")
I'm facing the exact same issue. Have tried deleting .kibana\_2 and restarting. No luck. Next time it said to delete .kibana\_1. I have shut down all kibana instances, and I'm just working on this one. Help? ---
**Author:** ![mlemartien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mlemartien/32/30958_2.png) [@mlemartien](https://discuss.elastic.co/u/mlemartien)\ **Post date:** [November 19, 2018, 8:58am UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/4 "2018-11-19T08:58:58Z")
You remove .kibana\_2 and then it asks to remove .kibana\_1, and so on. I found the answer to my problem and it is a known issue - will paste the link to the workaround a bit later ---
**Author:** ![mlemartien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mlemartien/32/30958_2.png) [@mlemartien](https://discuss.elastic.co/u/mlemartien)\ **Post date:** [November 19, 2018, 9:01am UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/5 "2018-11-19T09:01:55Z")
Here's how to fix this (it worked for me): [https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0](https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0) Delete the indices: DELETE {{url}}:{{elastic\_api\_port}}/.kibana\_1 DELETE {{url}}:{{elastic\_api\_port}}/.kibana\_2 Create the role: POST {{url}}:{{elastic\_api\_port}}/\_xpack/security/role/fix\_kibana\_65 { "cluster": ["all"], "indices": [ { "names": [".tasks"], "privileges": ["create\_index", "create", "read"] } ] } Create the user: POST {{url}}:{{elastic\_api\_port}}/\_xpack/security/user/fixkibana65 { "password" : "your\_password\_here", "roles" : ["kibana\_system", "fix\_kibana\_65"], "full\_name" : "Fix Kibana", "email" : "abc@email.com" } Then use this user in kibana.yml ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [November 19, 2018, 5:42pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/6 "2018-11-19T17:42:08Z")
I'm having the same issue, but have xpack.security.enabled: false in kibana.yml ---
**Author:** ![John\_Morrison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_morrison/32/107691_2.png) [@John\_Morrison](https://discuss.elastic.co/u/John_Morrison)\ **Post date:** [November 19, 2018, 5:51pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/7 "2018-11-19T17:51:29Z")
I did as you said, but still getting the same loop of annoyance. ---
**Author:** ![John\_Morrison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_morrison/32/107691_2.png) [@John\_Morrison](https://discuss.elastic.co/u/John_Morrison)\ **Post date:** [November 19, 2018, 6:04pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/8 "2018-11-19T18:04:36Z")
``` indent prefor{"type":"log","@timestamp":"2018-11-19T18:02:21Z","tags": ["reporting","warning"],"pid":1602,"message":"Enabling the Chromium sandbox provides an additional layer of protection."} {"type":"log","@timestamp":"2018-11-19T18:02:21Z","tags": ["info","migrations"],"pid":1602,"message":"Creating index .kibana_1."} {"type":"log","@timestamp":"2018-11-19T18:02:51Z","tags": ["status","plugin:spaces@6.5.0","error"],"pid":1602,"state":"red","message":"Status changed from yellow to red - Request Timeout after 30000ms","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"error","@timestamp":"2018-11-19T18:02:51Z","tags": ["fatal","root"],"pid":1602,"level":"fatal","error":{"message":"Request Timeout after 30000ms","name":"Error","stack":"Error: Request Timeout after 30000ms\n at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:355:15\n at Timeout. (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:384:7)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)"},"message":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-11-19T18:02:59Z","tags": ["status","plugin:kibana@6.5.0","info"],"pid":1615,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} matted text by 4 spaces ``` ---
**Author:** ![John\_Morrison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_morrison/32/107691_2.png) [@John\_Morrison](https://discuss.elastic.co/u/John_Morrison)\ **Post date:** [November 19, 2018, 6:08pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/9 "2018-11-19T18:08:57Z")
``` {"type":"log","@timestamp":"2018-11-19T18:03:01Z","tags": ["info","migrations"],"pid":1615,"message":"Creating index .kibana_1."} {"type":"log","@timestamp":"2018-11-19T18:03:01Z","tags": ["warning","migrations"],"pid":1615,"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_1 and restarting Kibana."} ``` ---
**Author:** ![John\_Morrison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_morrison/32/107691_2.png) [@John\_Morrison](https://discuss.elastic.co/u/John_Morrison)\ **Post date:** [November 19, 2018, 6:14pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/10 "2018-11-19T18:14:00Z")
[same problem reported here](https://github.com/elastic/kibana/issues/25796) ---
**Author:** ![John\_Morrison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_morrison/32/107691_2.png) [@John\_Morrison](https://discuss.elastic.co/u/John_Morrison)\ **Post date:** [November 19, 2018, 6:54pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/11 "2018-11-19T18:54:45Z")
Woops! sorry for the alarm..... If you set back "cluster.routing.allocation.enable": null then all is fine 🙂 ---
**Author:** ![rog\_NB](https://avatars.discourse-cdn.com/v4/letter/r/5fc32e/32.png) [@rog\_NB](https://discuss.elastic.co/u/rog_NB)\ **Post date:** [November 20, 2018, 12:01pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/12 "2018-11-20T12:01:59Z")
Thank you miemartien That worked for me. Even if I had to use curl and -k for the https certs. Luckly, if you have on the same cluster many kibana instances... However, are any informations around about the "old" kibana user? Since that one is build in, you can't delete them. Any ideas, how to upgrade? thanks rog ---
**Author:** ![mlemartien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mlemartien/32/30958_2.png) [@mlemartien](https://discuss.elastic.co/u/mlemartien)\ **Post date:** [November 20, 2018, 12:50pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/13 "2018-11-20T12:50:41Z")
I believe you have to keep both users for now. Only when a bug fix comes out (probably with 6.5.1) you can revert back to your former configuration and delete the "fix" user and role. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 18, 2018, 12:57pm UTC](https://discuss.elastic.co/t/upgraded-from-6-4-2-to-6-5-0-says-kibana-server-is-not-ready-yet/156994/14 "2018-12-18T12:57:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.