Upgraded ES 6.0.0-alpha1 to 6.5.1 , launching ES throw error

Hi,

I wanted to upgrade kibana from 6.0 to 6.5 to use the APM feature. So I did and i get "kibana server is not ready yet" on my 5601 port. I thought it was because my ES was still in version 6.0 so I did upgrade it to 6.5 and now I get this error when launching ES :

[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [aggs-matrix-stats]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [analysis-common]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [ingest-common]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [lang-expression]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [lang-mustache]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [lang-painless]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [mapper-extras]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [parent-join]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [percolator]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [rank-eval]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [reindex]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [repository-url]
[2018-11-28T10:42:50,764][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [transport-netty4]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [tribe]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-ccr]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-core]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-deprecation]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-graph]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-logstash]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-ml]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-monitoring]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-rollup]
[2018-11-28T10:42:50,765][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-security]
[2018-11-28T10:42:50,770][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-sql]
[2018-11-28T10:42:50,770][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-upgrade]
[2018-11-28T10:42:50,770][INFO ][o.e.p.PluginsService     ] [ldtHYSw] loaded module [x-pack-watcher]
[2018-11-28T10:42:50,771][INFO ][o.e.p.PluginsService     ] [ldtHYSw] no plugins loaded
[2018-11-28T10:43:00,570][INFO ][o.e.x.s.a.s.FileRolesStore] [ldtHYSw] parsed [0] roles from file [/etc/elasticsearch/roles.yml]
[2018-11-28T10:43:01,589][INFO ][o.e.x.m.j.p.l.CppLogMessageHandler] [ldtHYSw] [controller/11550] [Main.cc@109] controller (64 bit): Version 6.5.1 (Build 1c5fe241dd9aea) Copyright (c) 2018 Elasticsearch BV
[2018-11-28T10:43:02,313][DEBUG][o.e.a.ActionModule       ] [ldtHYSw] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security
[2018-11-28T10:43:04,352][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [ldtHYSw] fatal error in thread [main], exiting
java.lang.AssertionError: [.kibana/fQ9afSPoTpGBF5B6VG4sWA]multiple types are only allowed on pre 6.x indices but version is: [6.0.0-alpha1]
	at org.elasticsearch.index.IndexSettings.<init>(IndexSettings.java:472) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.index.IndexSettings.<init>(IndexSettings.java:416) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.checkMappingsCompatibility(MetaDataIndexUpgradeService.java:145) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.upgradeIndexMetaData(MetaDataIndexUpgradeService.java:95) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.gateway.GatewayMetaState.upgradeMetaData(GatewayMetaState.java:243) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.gateway.GatewayMetaState.<init>(GatewayMetaState.java:87) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.node.Node.<init>(Node.java:499) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.node.Node.<init>(Node.java:265) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:212) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:212) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:127) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.5.1.jar:6.5.1]
	at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) ~[elasticsearch-6.5.1.jar:6.5.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:86) ~[elasticsearch-6.5.1.jar:6.5.1]

It looks like something is still in 6.0. Does someone have a clue ? Thank you
Btw im on a debian server and I have Logstash(5.5.1), Kibana, ES, and APM Server (6.5.1)

I got it.
I had some indices that were not incompatible with ElasticSearch 6.5.1. I didn't needed them so i deleted them directly in /var/lib/elasticsearch/nodes.

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