# Kibana not work after upgrade **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [March 2, 2021, 1:54pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964 "2021-03-02T13:54:38Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pauldon2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pauldon2/32/32079_2.png) [@pauldon2](https://discuss.elastic.co/u/pauldon2)\ **Post date:** [March 2, 2021, 1:54pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964/1 "2021-03-02T13:54:38Z")
I have ELK cluster with ver. 6.6.2-oss Works in docker. Last week I upgraded to version 6.8.14 (basic). Elasticsearch works without any problems. But any attempts to switch to kibana other than version 6.6.2-oss end in failure. There are no error messages in the logs - port 5601 is available - now I get a message "Kibana server is not ready yet". curl returns the following code - curl -X GET "localhost:5601/status" -I "HTTP/1.1 503 Service Unavailable" What could be the problem? ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [March 2, 2021, 2:02pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964/2 "2021-03-02T14:02:57Z")
Something is preventing Kibana from starting correctly. Check the Kibana logs for more info. ---
**Author:** ![pauldon2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pauldon2/32/32079_2.png) [@pauldon2](https://discuss.elastic.co/u/pauldon2)\ **Post date:** [March 2, 2021, 2:29pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964/3 "2021-03-02T14:29:58Z")
Any error messages in logs. Several warnings. "{"type":"log","@timestamp":"2021-03-02T13:00:05Z","tags":["warning","elasticsearch","config","deprecation"],"pid":1,"message":"Config key "url" is deprecated. It has been replaced with "hosts""}" "{"type":"log","@timestamp":"2021-03-02T13:00:07Z","tags":["security","warning"],"pid":1,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml"}" "{"type":"log","@timestamp":"2021-03-02T13:00:07Z","tags":["security","warning"],"pid":1,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}" "{"type":"log","@timestamp":"2021-03-02T13:00:14Z","tags":["reporting","browser-driver","warning"],"pid":1,"message":"Enabling the Chromium sandbox provides an additional layer of protection."}" "{"type":"log","@timestamp":"2021-03-02T13:00:14Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"}" "{"type":"log","@timestamp":"2021-03-02T13:00:20Z","tags":["warning","task\_manager"],"pid":1,"message":"Task vis\_telemetry "oss\_telemetry-vis\_telemetry" failed in attempt to run: [version\_conflict\_engine\_exception] [\_doc][oss\_telemetry-vis\_telemetry]: version conflict, required seqNo [66], primary term [2]. current document has seqNo [67] and primary term [2], with { index\_uuid="PTFkNwK1SRKJ9qrCj7g2Sw" & shard="0" & index=".kibana\_task\_manager" }"}" "{"type":"log","@timestamp":"2021-03-02T13:00:20Z","tags":["warning","migrations"],"pid":1,"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."}" "{"type":"log","@timestamp":"2021-03-02T13:01:20Z","tags":["warning","task\_manager"],"pid":1,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."}" ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [March 2, 2021, 2:41pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964/4 "2021-03-02T14:41:57Z")
> 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. This is the relevant part. A migration failed. Please check out the documentation: > **[Saved object migrations | Kibana Guide \[6.8\] | Elastic](https://www.elastic.co/guide/en/kibana/6.8/upgrade-migrations.html#upgrade-migrations-errors)** ---
**Author:** ![pauldon2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pauldon2/32/32079_2.png) [@pauldon2](https://discuss.elastic.co/u/pauldon2)\ **Post date:** [March 2, 2021, 3:24pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964/5 "2021-03-02T15:24:44Z")
I have read this document. I have made several attempts to upgrade. The first few times I stopped and stuck my production docker with kibana. And I waited for about 20 minutes. Then I brought up the docker image with kibana on a separate instance and waited for about an hour. In both cases, kibana didn't work. The old image (6.6.2-oss) on the production server will rise almost instantly. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 30, 2021, 3:25pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-upgrade/265964/6 "2021-03-30T15:25:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.