# Upgrade of Kibana from 7.7.1 to 7.8.0 **URL:** \ **Category:** Kibana\ **Created:** [June 26, 2020, 5:48pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895 "2020-06-26T17:48:36Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![drewlander](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@drewlander](https://discuss.elastic.co/u/drewlander)\ **Post date:** [June 26, 2020, 5:48pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/1 "2020-06-26T17:48:37Z")
I upgraded from Kibana 7.7.1 to 7.8.0 (the elastic search cluster is now running 7.8.0) When starting Kibana, I get the following error message: `kibana: FATAL Error: Document contains at least one immense term in field="upgrade-assistant-reindex-operation.errorMessage" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[91, 105, 110, 100, 101, 120, 95, 99, 114, 101, 97, 116, 105, 111, 110, 95, 101, 120, 99, 101, 112, 116, 105, 111, 110, 93, 32, 102, 97, 105]...', original message: bytes can be at most 32766 in length; got 43360` `kibana.service: main process exited, code=exited, status=1/FAILURE Unit kibana.service entered failed state.` Then it restarts but will not go any further because: `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_17 and restarting Kibana."}` How can I fix the original message about the field="upgrade-assistant-reindex-operation.errorMessage ? Thank you ---
**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\ **Post date:** [June 29, 2020, 11:01am UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/2 "2020-06-29T11:01:17Z")
Hi @drewlander, I'd encourage you to go through [https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#upgrade-migrations-process](https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#upgrade-migrations-process) and in particular try [this instruction](https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#upgrade-migrations-errors). It seems something unexpected has happened during migration so that Kibana stuck in this tate. Best, Oleg ---
**Author:** ![drewlander](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@drewlander](https://discuss.elastic.co/u/drewlander)\ **Post date:** [June 29, 2020, 6:41pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/3 "2020-06-29T18:41:18Z")
thank you @azasypkin for the link I have deleted the referenced .kibana17, and restarted, and I get the same error. I downgraded kibana, and kibana is up and working. I went to 8.0 upgrade assistant and it did not have any issues reported. Is this error message saying that the field "upgrade-assistant-reindex-operation.errorMessage" is not big enough to hold the error message? Is the error message elsewhere? How can I find out what is causing kibana to not like the migration? Am I missing something important in the documentation you sent? Thank you ---
**Author:** ![drewlander](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@drewlander](https://discuss.elastic.co/u/drewlander)\ **Post date:** [July 6, 2020, 5:11pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/4 "2020-07-06T17:11:22Z")
anyone? ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [July 6, 2020, 5:39pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/5 "2020-07-06T17:39:14Z")
I upgraded two dev cluster and both had problem on one node, didn't restart kibana. other two worked. something definitely wrong or some kind of bug. The way I fix is to save config file remove rpm. delete all binary /usr/share/kibana recreate old uid/gid (same as other cluster node) reinstall rpm copy back original config file ---
**Author:** ![adamS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adams/32/56896_2.png) [@adamS](https://discuss.elastic.co/u/adamS)\ **Post date:** [July 25, 2020, 2:48pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/6 "2020-07-25T14:48:15Z")
I'm also getting this error when trying to migrate from Kibana 7.7.1 to 7.8.0. I've tried deleting the new .kibana index and trying again, but the error happens every time. Also tried a new VM with no luck. Has anyone found a solution? ``` {"type":"log","@timestamp":"2020-07-25T14:45:01Z","tags":["fatal","root"],"pid":15830,"message":"{ Error: Document contains at least one immense term in field=\"upgrade-assistant-reindex-operation.errorMessage\" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[69, 114, 114, 111, 114, 58, 32, 82, 101, 105, 110, 100, 101, 120, 105, 110, 103, 32, 102, 97, 105, 108, 101, 100, 58, 32, 123, 34, 99, 111]...', original message: bytes can be at most 32766 in length; got 33210\n at Object.write (/usr/share/kibana/src/core/server/saved_objects/migrations/core/elastic_index.js:152:21)\n at process._tickCallback (internal/process/next_tick.js:68:7)\n detail:\n { index:\n { _index: '.kibana_10',\n _type: '_doc',\n _id:\n 'upgrade-assistant-reindex-operation:1dfe8200-6a2e-11ea-867b-779f318d4c7e',\n status: 400,\n error: [Object] } } }"} ``` ---
**Author:** ![adamS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adams/32/56896_2.png) [@adamS](https://discuss.elastic.co/u/adamS)\ **Post date:** [July 25, 2020, 3:20pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/7 "2020-07-25T15:20:41Z")
I followed the workaround in [https://github.com/elastic/kibana/issues/71642#issuecomment-658975833](https://github.com/elastic/kibana/issues/71642#issuecomment-658975833) and was able to upgrade successfully to 7.8.0 ---
**Author:** ![drewlander](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@drewlander](https://discuss.elastic.co/u/drewlander)\ **Post date:** [July 27, 2020, 12:56pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/8 "2020-07-27T12:56:41Z")
That worked like a charm, thank you! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 24, 2020, 12:56pm UTC](https://discuss.elastic.co/t/upgrade-of-kibana-from-7-7-1-to-7-8-0/238895/9 "2020-08-24T12:56:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.