# Error migrating after upgrading to 7.11

**URL:** <https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928>\
**Category:** Kibana\
**Created:** [February 10, 2021, 8:32pm UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928 "2021-02-10T20:32:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![stephan13360](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@stephan13360](https://discuss.elastic.co/u/stephan13360)\
**Post date:** [February 10, 2021, 8:32pm UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/1 "2021-02-10T20:32:38Z")

</div>

I just upgraded my Elasticsearch / Kibana from 7.10.2 to 7.11 and now Kibana logs the following error when trying to run the migration:

```auto
{
  "type": "log",
  "@timestamp": "2021-02-10T20:11:18+01:00",
  "tags": ["fatal", "root"],
  "pid": 122860,
  "message": "Error: Document \"71198d10-25cf-11eb-9cdc-7787ad093e5e\" has property \"ingest_manager_settings\" which belongs to a more recent version of Kibana [7.10.0]. The last known version is [undefined]\n at /usr/share/kibana/src/core/server/saved_objects/migrations/core/document_migrator.js:254:27\n at Array.find (<anonymous>)\n at nextUnmigratedProp (/usr/share/kibana/src/core/server/saved_objects/migrations/core/document_migrator.js:240:21)\n at applyMigrations (/usr/share/kibana/src/core/server/saved_objects/migrations/core/document_migrator.js:168:18)\n at DocumentMigrator.transformAndValidate [as transformDoc] (/usr/share/kibana/src/core/server/saved_objects/migrations/core/document_migrator.js:154:43)\n at /usr/share/kibana/src/core/server/saved_objects/migrations/core/document_migrator.js:50:19\n at Immediate.<anonymous> (/usr/share/kibana/src/core/server/saved_objects/migrations/core/migrate_raw_docs.js:65:17)\n at processImmediate (internal/timers.js:461:21) {\n data: {\n type: 'ingest_manager_settings',\n id: '71198d10-25cf-11eb-9cdc-7787ad093e5e',\n attributes: {\n agent_auto_upgrade: true,\n package_auto_upgrade: true,\n kibana_urls: [Array]\n },\n references: [],\n migrationVersion: { ingest_manager_settings: '7.10.0' },\n updated_at: '2020-11-13T16:44:05.088Z'\n },\n isBoom: true,\n isServer: false,\n output: {\n statusCode: 422,\n payload: {\n statusCode: 422,\n error: 'Unprocessable Entity',\n message: 'Document \"71198d10-25cf-11eb-9cdc-7787ad093e5e\" has property \"ingest_manager_settings\" which belongs to a more recent version of Kibana [7.10.0]. The last known version is [undefined]'\n },\n headers: {}\n }\n}"
}

```

For me the line "The last known version is [undefined]" looks like Kibana 7.11 can't determine its own version correctly and thinks 7.10.0 is newer?

Anyone else seeing this or has an idea why kibana thinks its version is undefined?

---

<div class="post-metadata">

**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:** [February 10, 2021, 10:21pm UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/2 "2021-02-10T22:21:23Z")

</div>

Is there anything else in the logs?  
Does your browser show anything in the console?

---

<div class="post-metadata">

**Author:** ![stephan13360](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@stephan13360](https://discuss.elastic.co/u/stephan13360)\
**Post date:** [February 11, 2021, 8:39am UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/3 "2021-02-11T08:39:42Z")

</div>

This is the only line appearing in the log after the upgrade.  
I ran the migration again, by deleting the .kibana\_N+1 and .kibana\_task\_manager\_N index, but only got the same log entry again.

The Webinterface only shows: "Kibana server is not ready yet".

---

<div class="post-metadata">

**Author:** ![hermlam](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@hermlam](https://discuss.elastic.co/u/hermlam)\
**Post date:** [February 11, 2021, 9:23am UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/4 "2021-02-11T09:23:38Z")

</div>

I am getting many errors, everywhere, in Fleet, in Discover, Stack management etc.

---

<div class="post-metadata">

**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:** [February 11, 2021, 10:15am UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/5 "2021-02-11T10:15:52Z")

</div>

@hermlam Please open a new topic with more information, include all Kibana server logs and screenshots of anything you see in the browser.

---

<div class="post-metadata">

**Author:** ![stephan13360](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@stephan13360](https://discuss.elastic.co/u/stephan13360)\
**Post date:** [February 11, 2021, 12:42pm UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/7 "2021-02-11T12:42:09Z")

</div>

I found the problem / solution.  
I had "xpack.fleet.enabled: false" in my kibana.yml. The Errors message talks about "ingest\_manager\_settings", which is part of Fleet. After enabling it an deleting the .kibana\_N+1 index, Kibana startet again.

---

<div class="post-metadata">

**Author:** ![skh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skh/32/38637_2.png) [@skh](https://discuss.elastic.co/u/skh)\
**Post date:** [February 11, 2021, 1:22pm UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/8 "2021-02-11T13:22:57Z")

</div>

Thank you @stephan13360 for letting us know!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 11, 2021, 1:23pm UTC](https://discuss.elastic.co/t/error-migrating-after-upgrading-to-7-11/263928/9 "2021-03-11T13:23:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
