UnsupportedFormat version either too old or too new for this mongod

Hi,

Mongo cluster stopped working, presumably after i started using version 5.0
I’m using MongoDb for a PoC and i’m stuck at startup.

Any help or hint on how to solve below?

Thanks!

{"t":{"$date":"2021-07-28T12:46:17.229+00:00"},"s":"I",  "c":"STORAGE",  "id":22251,   "ctx":"initandlisten","msg":"Dropping unknown ident","attr":{"ident":"index-0--7843749110687358905"}}

{"t":{"$date":"2021-07-28T12:46:17.230+00:00"},"s":"I",  "c":"STORAGE",  "id":22253,   "ctx":"initandlisten","msg":"Found index from unfinished build","attr":{"namespace":"aphrodite.parameters","uuid":{"uuid":{"$uuid":"6d344add-d600-4113-b4a4-a64ca6732068"}},"index":"FixedId_1_OrganizationId_1","buildUUID":{"uuid":{"$uuid":"44e900a4-8d44-4b9c-afd7-ebff582e89c5"}}}}

{"t":{"$date":"2021-07-28T12:46:17.230+00:00"},"s":"I",  "c":"STORAGE",  "id":22253,   "ctx":"initandlisten","msg":"Found index from unfinished build","attr":{"namespace":"aphrodite.parameters","uuid":{"uuid":{"$uuid":"6d344add-d600-4113-b4a4-a64ca6732068"}},"index":"_id_1_OrganizationId_1","buildUUID":{"uuid":{"$uuid":"7ae29318-a69e-4838-a2d5-b51d0a9dd758"}}}}

{"t":{"$date":"2021-07-28T12:46:17.230+00:00"},"s":"I",  "c":"STORAGE",  "id":22253,   "ctx":"initandlisten","msg":"Found index from unfinished build","attr":{"namespace":"aphrodite.deviceType","uuid":{"uuid":{"$uuid":"497e3dc7-acd0-4c45-b6ae-543f4c1ef009"}},"index":"fixedTypeId_1_organizationId_1","buildUUID":{"uuid":{"$uuid":"88ec91b8-763d-4a51-b8f7-82fbdfd79cd4"}}}}

{"t":{"$date":"2021-07-28T12:46:17.230+00:00"},"s":"I",  "c":"STORAGE",  "id":22257,   "ctx":"initandlisten","msg":"Dropping internal ident","attr":{"ident":"internal-1--7843749110687358905"}}

{"t":{"$date":"2021-07-28T12:46:17.231+00:00"},"s":"I",  "c":"STORAGE",  "id":5071100, "ctx":"initandlisten","msg":"Clearing temp directory"}

{"t":{"$date":"2021-07-28T12:46:17.231+00:00"},"s":"I",  "c":"STORAGE",  "id":20660,   "ctx":"initandlisten","msg":"Index build: restarting","attr":{"buildUUID":{"uuid":{"$uuid":"44e900a4-8d44-4b9c-afd7-ebff582e89c5"}},"collectionUUID":{"uuid":{"$uuid":"6d344add-d600-4113-b4a4-a64ca6732068"}},"namespace":"aphrodite.parameters"}}

{"t":{"$date":"2021-07-28T12:46:17.231+00:00"},"s":"F",  "c":"-",        "id":23093,   "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28579,"error":"UnsupportedFormat: Unable to find metadata for table:index-4-3793787578084132147 Index: {name: _id_1_OrganizationId_1, ns: aphrodite.parameters} - version either too old or too new for this mongod.","file":"src/mongo/db/storage/wiredtiger/wiredtiger_index.cpp","line":514}}

{"t":{"$date":"2021-07-28T12:46:17.231+00:00"},"s":"F",  "c":"-",        "id":23094,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}

{"t":{"$date":"2021-07-28T12:46:17.231+00:00"},"s":"F",  "c":"CONTROL",  "id":4757800, "ctx":"initandlisten","msg":"Writing fatal message","attr":{"message":"Got signal: 6 (Aborted).\n"}}

@Joao_Passos Did you upgrade to 5.0, if so from what version ?

1 Like

thank you for reading my question Chris
it’s from 4.4.
I say “presumably” because I’m not sure if they started to fail after or if it was already happening before.

Sorry for the lack of info, I’ve picked up from another college that is on vacation

I suggest you drop back to 4.4 and first follow the upgrade to 4.4 guide in case steps from previous upgrade were missed, this is a likely scenario.

Then follow the 5.0 upgrade guide to get to 5.0.

The guides will mention it, but here it is. Take backups before executing these procedures.

same error after downgrade, i looks like is not related

{“t”:{"$date":“2021-07-28T14:17:57.358+00:00”},“s”:“F”, “c”:"-", “id”:23095, “ctx”:“initandlisten”,“msg”:“Fatal assertion”,“attr”:{“msgid”:28579,“error”:“UnsupportedFormat: Unable to find metadata for table:index-4-3793787578084132147 Index: {name: _id_1_OrganizationId_1, ns: aphrodite.parameters} - version either too old or too new for this mongod.”,“file”:“src/mongo/db/storage/wiredtiger/wiredtiger_index.cpp”,“line”:526}}

Are you sure it was 4.2? This error seems to be related to index versions, which would indicated a much earlier version.

Try inspecting the logs for the version that was running previously. You can also inspect the FTDC data to find this:

Hi Chris,

It’s 4.4.4, we only started this PoC in February 2021

root@6d3296b26edb:/data/db/diagnostic.data# bsondump --quiet /data/db/diagnostic.data/metrics.2021-07-08T14-36-58Z-00000 | jq -s ‘.[] | select(.type == {"$numberInt": “0”})| .doc.buildInfo.version’
“4.4.4”

1 Like

I couldn’t figure out what happened so I deleted the db folder from both replica sets and they resynced after restarting.

Thank you for your support @chris