# KIbana "Kibana server is not ready yet" -- routing disabled during upgrade **URL:** \ **Category:** Kibana\ **Created:** [December 1, 2020, 5:05pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245 "2020-12-01T17:05:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![OntheHighSeas](https://avatars.discourse-cdn.com/v4/letter/o/848f3c/32.png) [@OntheHighSeas](https://discuss.elastic.co/u/OntheHighSeas)\ **Post date:** [December 1, 2020, 5:05pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/1 "2020-12-01T17:05:44Z")
Hi. So I think I made the mistake of upgrading to v7.10 Kibana with my cluster routing disabled, and as a result Kibana is stuck migrating. It's constantly producing log messages along the line of; ``` ["info", "savedobjects-service"], "pid":5709,"message":"Detected mapping change in \"properties.originId\"" ``` Stopping Kibana and deleting the latest instance of .kibana\_n and restarting the Kibana just produces another. I've also enabled routing etc. I don't want to lose all the dashboards, but I'm not sure what the solution is, can anyone help. I've read lots of prior posts on this but there doesn't seem to be a clear solution. thanks ---
**Author:** ![dbannik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dbannik/32/80538_2.png) [@dbannik](https://discuss.elastic.co/u/dbannik)\ **Post date:** [December 9, 2020, 9:15pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/2 "2020-12-09T21:15:14Z")
I also get this error after upgrading to 7.10.1 ---
**Author:** ![kid4git](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kid4git/32/81966_2.png) [@kid4git](https://discuss.elastic.co/u/kid4git)\ **Post date:** [January 9, 2021, 7:09am UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/4 "2021-01-09T07:09:24Z")
I had the same issue after ugprading to 7.10.1. The solution I came up with was this: Before upgrading, export all saved objects at Stack Management \> Saved objects. Stop Kibana. Delete the .kibana\_\* and .kibana\_task\_manager\_\* indexes: ```auto $ for index in .kibana .kibana_1 .kibana_2 .kibana_3 .kibana_4 .kibana_task_manager_1 .kibana_task_manager_2 .kibana_task_manager_3; do curl -XDELETE http://localhost:9200/$index; done {"acknowledged":true}{"acknowledged":true}... ``` Upgrade and start Kibana. Reimport the previously exported saved objects at Stack Management \> Saved objects. This worked pretty well. Despite some few errors about canvas-workpad-template stuff ("Unsupported object type"), all my dashboards, index patterns and so on will be there and working again. Not sure if the .kibana\_task\_manager\_\* really needed to be deleted, but it worked for me. ---
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [January 11, 2021, 12:14pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/5 "2021-01-11T12:14:05Z")
Every time Kibana is restarted, it checks if a migration is required. It will perform a migration if either documents are outdated or if the mappings are different to what Kibana expects. The latter is what triggers a migration in your case. As per the error message, `properties.originId` has a different mapping to what Kibana expects. Do you have any index templates that might have an `indexPattern` that matches `.kibana*`? Could you share the output of `GET /.kibana/_mapping`? ---
**Author:** ![IslandMan](https://avatars.discourse-cdn.com/v4/letter/i/977dab/32.png) [@IslandMan](https://discuss.elastic.co/u/IslandMan)\ **Post date:** [January 25, 2021, 2:33pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/6 "2021-01-25T14:33:36Z")
Hey, so I'm running into the same issue as mentioned by the original reporter. Luckily I have s3 snapshotting enabled on `.kibana*` so I have the liberty to experiment back and forth. Doing the export/import procedure does not cut it for me. I end up with missing dashboards unfortunately. If pasted the mapping on pastebin: [https://pastebin.com/yrGSbmg6](https://pastebin.com/yrGSbmg6) I hope this provides some clue as to what's going on here. I'm upgrading from 7.8.0. ---
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [January 25, 2021, 6:24pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/7 "2021-01-25T18:24:18Z")
@IslandMan could you restore your snapshot, and then attempt a migration and post all of the logs from the first time the upgrade migration runs? Please open a new thread and ping me. ---
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [January 26, 2021, 2:50pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/8 "2021-01-26T14:50:53Z")
If anyone else stumbles on this thread, @IslandMan's issue was solved in [Upgrading Kibana to 7.10.2 hangs while migrating](https://discuss.elastic.co/t/upgrading-kibana-to-7-10-2-hangs-while-migrating/262197) ---
**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, 2:51pm UTC](https://discuss.elastic.co/t/kibana-kibana-server-is-not-ready-yet-routing-disabled-during-upgrade/257245/9 "2021-02-23T14:51:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.