# Error migrating kibana 5.4 to 5.6
**URL:** https://discuss.elastic.co/t/error-migrating-kibana-5-4-to-5-6/170955
**Category:** Kibana
**Created:** [March 5, 2019, 4:51pm UTC](https://discuss.elastic.co/t/error-migrating-kibana-5-4-to-5-6/170955 "2019-03-05T16:51:04Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@parosio](https://discuss.elastic.co/u/parosio)
#### Post date: [March 5, 2019, 4:51pm UTC](https://discuss.elastic.co/t/error-migrating-kibana-5-4-to-5-6/170955/1 "2019-03-05T16:51:05Z")
Hello,
we're having trouble in migrating .kibana index from 5.4.0 to 5.6.5 (in order to prepare it to a final migration to 6.5).
We're testing it in a single-node environment.
We follow the [instructions](https://www.elastic.co/guide/en/kibana/5.6/migrating-6.0-index.html) for a manual upgrade:
1. make a copy of current .kibana =\> .kibana-backup-5-4
2. Set `.kibana` index to read-only
3. Create a .kibana-6 with the new mapping, with both `"index.mapper.dynamic": false,` and `"index.mapping.single_type": true`
2.1 Reindex `.kibana` into `.kibana-6`
2.2 Alias `.kibana-6` to `.kibana` and remove legacy `.kibana` index
When starting kibana we have errors from the plugins, as the index rejects multiple types:
```
log [16:02:47.782] [error][status][plugin:xpack_main@5.6.5] Status changed from yellow to red - [illegal_argument_exception] Rejecting mapping update to [.kibana-6] as the final mapping would have more than 1 type: [doc, config]
...
log [16:02:47.791] [error][status][plugin:searchprofiler@5.6.5] Status changed from uninitialized to red - [illegal_argument_exception] Rejecting mapping update to [.kibana-6] as the final mapping would have more than 1 type: [doc, config]
```
then it continues trying to create new type(s) in .kibana:
```
log [16:02:48.487] [info][status][plugin:timelion@5.6.5] Status changed from uninitialized to green - Ready
log [16:02:48.494] [info][listening] Server running at http://localhost:5601
log [16:02:48.496] [error][status][ui settings] Status changed from uninitialized to red - Elasticsearch plugin is red
ops [16:02:50.131] memory: 916.1MB uptime: 0:06:48 load: [1.20 1.05 0.80] delay: 2.538
log [16:02:50.291] [debug][plugin] Checking Elasticsearch version
log [16:02:50.318] [info][elasticsearch] Adding mappings to kibana index for SavedObject type "config"
log [16:02:50.735] [debug][esqueue][reporting][worker] jsvypf730e6yb7e9b7c1b769 - querying for outstanding jobs
log [16:02:50.741] [debug][esqueue][reporting][worker] jsvypf730e6yb7e9b7c1b769 - 0 outstanding jobs returned
log [16:02:52.842] [debug][plugin] Checking Elasticsearch version
log [16:02:52.864] [info][elasticsearch] Adding mappings to kibana index for SavedObject type "config"
log [16:02:53.748] [debug][esqueue][reporting][worker] jsvypf730e6yb7e9b7c1b769 - querying for outstanding jobs
log [16:02:53.755] [debug][esqueue][reporting][worker] jsvypf730e6yb7e9b7c1b769 - 0 outstanding jobs returned
ops [16:02:55.132] memory: 917.2MB uptime: 0:06:53 load: [1.10 1.03 0.80] delay: 2.328
```
In Elasticsearch, we keep having:
```
[2019-03-05T17:03:43,792][DEBUG][o.e.a.a.i.m.p.TransportPutMappingAction] [mCMhoMa] failed to put mappings on indices [[[.kibana-6/mRl4HsY_TWKlH8aItayVzw]]], type [config]
java.lang.IllegalArgumentException: Rejecting mapping update to [.kibana-6] as the final mapping would have more than 1 type: [doc, config]
...
```
We've tried also with the migration UI from x-pack, but with no better results.
Any advice is welcome,
Regards
---
### Author:  [@parosio](https://discuss.elastic.co/u/parosio)
#### Post date: [March 6, 2019, 3:18pm UTC](https://discuss.elastic.co/t/error-migrating-kibana-5-4-to-5-6/170955/2 "2019-03-06T15:18:15Z")
Seems that moving through 5.6 isn't really necessary. It's cause of troubles, actually.
It'd been sufficient to move data to a fresh new 6.6 installation. Then, the new mapping has been put for .kibana-6, and the old .kibana documents have been reindexed to the newly created .kibana-6.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 3, 2019, 3:18pm UTC](https://discuss.elastic.co/t/error-migrating-kibana-5-4-to-5-6/170955/3 "2019-04-03T15:18:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.