# "Failed to read or upgrade local state, exiting..." when starting ES instance **URL:** https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330 **Category:** Elasticsearch **Created:** [December 28, 2018, 9:43am UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330 "2018-12-28T09:43:05Z") **Posts on this page:** 7 **Page:** 1
### Author: ![Valentin\_Courtois](https://avatars.discourse-cdn.com/v4/letter/v/3e96dc/32.png) [@Valentin\_Courtois](https://discuss.elastic.co/u/Valentin_Courtois) #### Post date: [December 28, 2018, 9:43am UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/1 "2018-12-28T09:43:05Z")
Hello, I'm developing a kibana plugin, without my ES instance I'm completely dead. Yesterday ES instance would start normally, but today it doesn't work for some reason. Error logs are: ```auto > [2018-12-28T10:38:41,715][ERROR][o.e.g.GatewayMetaState] [LFR016701] failed to read or upgrade local state, exiting... > java.io.IOException: failed to find global metadata [generation: 68] > at org.elasticsearch.gateway.MetaStateService.loadFullState(MetaStateService.java:86) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.gateway.GatewayMetaState.upgradeMetaData(GatewayMetaState.java:158) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.gateway.GatewayMetaState.(GatewayMetaState.java:110) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.node.Node.(Node.java:472) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.node.Node.(Node.java:251) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:211) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:211) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:325) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [elasticsearch-cli-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) [elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > [2018-12-28T10:38:41,731][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [LFR016701] uncaught exception in thread [main] > org.elasticsearch.bootstrap.StartupException: ElasticsearchException[failed to bind service]; nested: IOException[failed to find global metadata [generation: 68]]; > at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:163) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > Caused by: org.elasticsearch.ElasticsearchException: failed to bind service > at org.elasticsearch.node.Node.(Node.java:579) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.node.Node.(Node.java:251) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:211) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:211) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:325) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > ... 6 more > Caused by: java.io.IOException: failed to find global metadata [generation: 68] > at org.elasticsearch.gateway.MetaStateService.loadFullState(MetaStateService.java:86) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.gateway.GatewayMetaState.upgradeMetaData(GatewayMetaState.java:158) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.gateway.GatewayMetaState.(GatewayMetaState.java:110) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.node.Node.(Node.java:472) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.node.Node.(Node.java:251) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:211) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:211) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:325) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-7.0.0-SNAPSHOT.jar:7.0.0-SNAPSHOT] > ... 6 more ``` What should I do about this? (when I google "failed to find global metadata", nothing is found.) ---
### Author: ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov) #### Post date: [December 28, 2018, 7:25pm UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/2 "2018-12-28T19:25:00Z")
Did you pull/build a new version of elasticsearch recently? The data-level compatibility between snapshot version is not guaranteed. So, it's possible that some modification broke backward-compatibility with the previous revision. The simplest workaround here is to delete `data` directory in elasticsearch installation, but unfortunately, it will also wipe out all your data indexed in elasticsearch. ---
### Author: ![Valentin\_Courtois](https://avatars.discourse-cdn.com/v4/letter/v/3e96dc/32.png) [@Valentin\_Courtois](https://discuss.elastic.co/u/Valentin_Courtois) #### Post date: [December 28, 2018, 11:46pm UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/3 "2018-12-28T23:46:35Z")
Thanks for responding. In fact when it was working yesterday I was already on 7.0 0-snapshot. I'll try wour workaround soon enough and tell you if that fixes (I can do the rolling upgrade once again to get data back, I have a save.). ---
### Author: ![Valentin\_Courtois](https://avatars.discourse-cdn.com/v4/letter/v/3e96dc/32.png) [@Valentin\_Courtois](https://discuss.elastic.co/u/Valentin_Courtois) #### Post date: [January 2, 2019, 9:52am UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/4 "2019-01-02T09:52:08Z")
Using a new `data` directory did work. I still don't understand why it broke though, since when I copied old `data` directory's indices in the new one, it still worked. Worth keeping an eye on it. ---
### Author: ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov) #### Post date: [January 2, 2019, 5:00pm UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/5 "2019-01-02T17:00:15Z")
Is it possible that you downgraded elasticsearch somehow? ---
### Author: ![Valentin\_Courtois](https://avatars.discourse-cdn.com/v4/letter/v/3e96dc/32.png) [@Valentin\_Courtois](https://discuss.elastic.co/u/Valentin_Courtois) #### Post date: [January 3, 2019, 10:53am UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/6 "2019-01-03T10:53:25Z")
Not really downgraded. But what I think happened is that the other elasticsearch installed on machine (es 6.5.3, that _I thought_ was uninstalled, I just noticed it right now) started on its own on windows startup (as a service). And it might have broken `data` folder somehow. Is there a way I can uninstall this service? I'm not used to windows. ---
### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system) #### Post date: [January 31, 2019, 10:53am UTC](https://discuss.elastic.co/t/failed-to-read-or-upgrade-local-state-exiting-when-starting-es-instance/162330/7 "2019-01-31T10:53:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.