# Service not start , Format version is not supported

**URL:** <https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974>\
**Category:** CrateDB\
**Created:** [January 9, 2022, 8:21am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974 "2022-01-09T08:21:01Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahoboy468](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mahoboy468](https://community.cratedb.com/u/mahoboy468)\
**Post date:** [January 9, 2022, 8:21am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/1 "2022-01-09T08:21:01Z")

</div>

Hello,  
crate service not start after reboot OS,  
and have error  
but its worked fine before  
can anyone help me?  
thanks

```auto
2022-01-09T08:06:32,460][INFO][o.e.e.NodeEnvironment] [Jungfrau] using [1] data paths, mounts [[/ (/dev/sda2)]], net usable_space [20.4gb], net total_space [39.1gb], types [ext4]
[2022-01-09T08:06:32,477][INFO][o.e.e.NodeEnvironment] [Jungfrau] heap size [1.9gb], compressed ordinary object pointers [true]
[2022-01-09T08:06:33,348][ERROR][o.e.b.BootstrapProxy] [Jungfrau] Exception
org.elasticsearch.ElasticsearchException: failed to bind service
	at org.elasticsearch.node.Node.<init>(Node.java:651) ~[crate-server.jar:?]
	at io.crate.node.CrateNode.<init>(CrateNode.java:53) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy$1.<init>(BootstrapProxy.java:192) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy.setup(BootstrapProxy.java:192) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy.init(BootstrapProxy.java:266) [crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.init(CrateDB.java:158) [crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.execute(CrateDB.java:138) [crate-app.jar:4.6.1]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:81) [crate-server.jar:?]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [crate-cli.jar:?]
	at org.elasticsearch.cli.Command.main(Command.java:90) [crate-cli.jar:?]
	at io.crate.bootstrap.CrateDB.main(CrateDB.java:91) [crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.main(CrateDB.java:84) [crate-app.jar:4.6.1]
Caused by: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(SimpleFSIndexInput(path="/var/lib/crate/nodes/0/_state/segments_zm"))): 0 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 6.0 and later.
	at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:307) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:61) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:58) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:720) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:81) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:63) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.elasticsearch.gateway.PersistedClusterStateService.nodeMetadata(PersistedClusterStateService.java:266) ~[crate-server.jar:?]
	at org.elasticsearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:416) ~[crate-server.jar:?]
	at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:329) ~[crate-server.jar:?]
	at org.elasticsearch.node.Node.<init>(Node.java:270) ~[crate-server.jar:?]
	... 11 more
[2022-01-09T08:06:33,377][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [Jungfrau] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: org.elasticsearch.ElasticsearchException: failed to bind service
	at org.elasticsearch.bootstrap.StartupExceptionProxy.<init>(StartupExceptionProxy.java:30) ~[crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.init(CrateDB.java:162) ~[crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.execute(CrateDB.java:138) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:81) ~[crate-server.jar:?]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[crate-cli.jar:?]
	at org.elasticsearch.cli.Command.main(Command.java:90) ~[crate-cli.jar:?]
	at io.crate.bootstrap.CrateDB.main(CrateDB.java:91) ~[crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.main(CrateDB.java:84) ~[crate-app.jar:4.6.1]
Caused by: org.elasticsearch.ElasticsearchException: failed to bind service
	at org.elasticsearch.node.Node.<init>(Node.java:651) ~[crate-server.jar:?]
	at io.crate.node.CrateNode.<init>(CrateNode.java:53) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy$1.<init>(BootstrapProxy.java:192) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy.setup(BootstrapProxy.java:192) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy.init(BootstrapProxy.java:266) ~[crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.init(CrateDB.java:158) ~[crate-app.jar:4.6.1]
	... 6 more
Caused by: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(SimpleFSIndexInput(path="/var/lib/crate/nodes/0/_state/segments_zm"))): 0 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 6.0 and later.
	at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:307) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:61) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:58) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:720) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:81) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:63) ~[lucene-core-8.8.2.jar:8.8.2 a92a05e195b775b30ca410bc0a26e8e79e7b3bfb - mdrob - 2021-04-06 16:33:27]
	at org.elasticsearch.gateway.PersistedClusterStateService.nodeMetadata(PersistedClusterStateService.java:266) ~[crate-server.jar:?]
	at org.elasticsearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:416) ~[crate-server.jar:?]
	at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:329) ~[crate-server.jar:?]
	at org.elasticsearch.node.Node.<init>(Node.java:270) ~[crate-server.jar:?]
	at io.crate.node.CrateNode.<init>(CrateNode.java:53) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy$1.<init>(BootstrapProxy.java:192) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy.setup(BootstrapProxy.java:192) ~[crate-app.jar:4.6.1]
	at org.elasticsearch.bootstrap.BootstrapProxy.init(BootstrapProxy.java:266) ~[crate-app.jar:4.6.1]
	at io.crate.bootstrap.CrateDB.init(CrateDB.java:158) ~[crate-app.jar:4.6.1]

```

---

<div class="post-metadata">

**Author:** ![proddata](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/proddata/32/1379_2.png) [@proddata](https://community.cratedb.com/u/proddata)\
**Post date:** [January 10, 2022, 7:24am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/2 "2022-01-10T07:24:11Z")

</div>

Did you upgrade your CrateDB installation?

---

<div class="post-metadata">

**Author:** ![mahoboy468](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mahoboy468](https://community.cratedb.com/u/mahoboy468)\
**Post date:** [January 10, 2022, 8:21am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/3 "2022-01-10T08:21:47Z")

</div>

no, CrateDB version is 4.6.1

---

<div class="post-metadata">

**Author:** ![proddata](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/proddata/32/1379_2.png) [@proddata](https://community.cratedb.com/u/proddata)\
**Post date:** [January 10, 2022, 5:00pm UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/4 "2022-01-10T17:00:01Z")

</div>

Could you share some info about your setup and what you did?  
Docker, linux packages, tar ball?

---

<div class="post-metadata">

**Author:** ![mahoboy468](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mahoboy468](https://community.cratedb.com/u/mahoboy468)\
**Post date:** [January 11, 2022, 8:20am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/5 "2022-01-11T08:20:06Z")

</div>

installed from Linux Packages  
Ubuntu 20.04

---

<div class="post-metadata">

**Author:** ![jayeff](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/jayeff/32/271_2.png) [@jayeff](https://community.cratedb.com/u/jayeff)\
**Post date:** [January 11, 2022, 8:25am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/6 "2022-01-11T08:25:08Z")

</div>

@mahoboy468 Any chance you did upgrade the `crate` package recently? Maybe happened during the reboot? When was your CrateDB cluster set up originally (rough timeframe)?

---

<div class="post-metadata">

**Author:** ![mahoboy468](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mahoboy468](https://community.cratedb.com/u/mahoboy468)\
**Post date:** [January 11, 2022, 8:30am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/7 "2022-01-11T08:30:52Z")

</div>

@jayeff No, it has not been updated. system worked fine, i think database files crashed after reboot.  
Can it be reindex or create new node folder and move prev node files to new node?

---

<div class="post-metadata">

**Author:** ![jayeff](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/jayeff/32/271_2.png) [@jayeff](https://community.cratedb.com/u/jayeff)\
**Post date:** [January 11, 2022, 8:45am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/8 "2022-01-11T08:45:30Z")

</div>

@mahoboy468 It’s difficult to tell what potentially happened or how to proceed without having much insight into your setup.

You could try to move away the data-folders and start with a fresh, empty data-folder. If you have a backup you could potentially restore the files from the backup. If your tables are replicated CrateDB would restore the data from the replica automatically.

---

<div class="post-metadata">

**Author:** ![mahoboy468](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mahoboy468](https://community.cratedb.com/u/mahoboy468)\
**Post date:** [January 11, 2022, 9:05am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/9 "2022-01-11T09:05:33Z")

</div>

@jayeff

system have 1 node, and i haven’t backup or snapshot  
i try this step and crate start fine without data, and Crate create nodes folder automatically

```auto
mv /var/lib/crate/nodes /var/lib/crate/nodes_org
systemctl start crate

```

so,

```auto
systemctl stop crate
mv /var/lib/crate/nodes_org/0/indices /var/lib/crate/nodes/0/
systemctl start crate

```

crate started, but not show any data  
Can i fix this problem only with indices folder and without old \_state folder ?

---

<div class="post-metadata">

**Author:** ![jayeff](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/jayeff/32/271_2.png) [@jayeff](https://community.cratedb.com/u/jayeff)\
**Post date:** [January 11, 2022, 10:04am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/10 "2022-01-11T10:04:54Z")

</div>

@mahoboy468 without backup or another node with replicated data I don’t know if you have a chance of restoring your data 😬

---

<div class="post-metadata">

**Author:** ![mahoboy468](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mahoboy468](https://community.cratedb.com/u/mahoboy468)\
**Post date:** [January 12, 2022, 5:43am UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/11 "2022-01-12T05:43:40Z")

</div>

@jayeff it’s very bad! other database engine have solutions for fix same problem! 😔

---

<div class="post-metadata">

**Author:** ![proddata](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/proddata/32/1379_2.png) [@proddata](https://community.cratedb.com/u/proddata)\
**Post date:** [January 12, 2022, 1:49pm UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/12 "2022-01-12T13:49:54Z")

</div>

I am sorry, that we don’t have better news for you.

It is hard to say what really happened here, without getting the full story. It could easily be a hardware fault or an unlucky case when Crate was turned off in a not graceful way (e.g. power loss). The core data layer of CrateDB provides transactional semantics on file level. I would consider a corruption during runtime very very unlikely. If the node would be part of a cluster with replication enabled, such a corruption would most likely self-heal, without users even noticing it.

---

<div class="post-metadata">

**Author:** ![amotl](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/amotl/32/617_2.png) [@amotl](https://community.cratedb.com/u/amotl)\
**Post date:** [January 12, 2022, 2:45pm UTC](https://community.cratedb.com/t/service-not-start-format-version-is-not-supported/974/13 "2022-01-12T14:45:00Z")

</div>

Dear @mahoboy468,

your observations indeed indicate that the Lucene data files got corrupted.

> It looks like the main directory file, [segments\_N](http://lucene.apache.org/core/old_versioned_docs/versions/3_5_0/fileformats.html#Segments%20File) is corrupted. This probably means that a power loss happened while a commit was running. \[1\]

Other resources like ["Format version is not supported" - Elasticsearch - Discuss the Elastic Stack](https://discuss.elastic.co/t/format-version-is-not-supported/69027) also indicate that there is no way to ordinarily recover from this situation.

In order to recover your data by [carving](https://en.wikipedia.org/wiki/File_carving) them out of the raw data files, you might want to look at the [Apache Luke](https://github.com/DmitryKey/luke) program, as roughly outlined at [The same full-text search engine for different pro... - Atlassian Community](https://community.atlassian.com/t5/Confluence-articles/The-same-full-text-search-engine-for-different-products/ba-p/1319832). You also might want to check out the Lucene CheckIndex program, see [Lucene and Solr's CheckIndex to the Rescue! - DZone](https://dzone.com/articles/lucene-and-solrs-checkindex).

Please note that running those programs on your data is completely out of scope for any serious recovery procedure related to CrateDB, I am hereby only sharing some resources with you to indicate how others might have rescued the situation as a last resort. There is no guarantee that this will bring back any of your data. Always take backups!

With kind regards,  
Andreas.

* * *

1. [How to repair corrupted lucene index? - Stack Overflow](https://stackoverflow.com/a/9969013)
