Upgrading from 5.5.4 to 5.6.3 keeping db says Snappy not supported

21:10:56.306 [info] Starting reporters with [{subscribers,[{select,{[{{[ae,epoch|'_'],counter,enabled},[],['$_']},{{[ae,epoch|'_'],gauge,enabled},[],['$_']}],aec_metrics_main,[value],default,true}},{select,{[{{[ae,epoch|'_'],'$1',enabled},[{'=/=','$1',counter},{'=/=','$1',gauge}],['$_']}],aec_metrics_main,default,default,true}}]}]
21:10:56.806 [error] CRASH REPORT Process <0.1395.0> with 0 neighbours crashed with reason: no match of right hand value {error,{db_open,"Corruption: Snappy not supported or corrupted Snappy compressed block contents"}} in mnesia_rocksdb:do_load_table/2 line 943
21:10:56.987 [error] CRASH REPORT Process <0.1409.0> with 0 neighbours crashed with reason: no match of right hand value {error,{db_open,"Corruption: Snappy not supported or corrupted Snappy compressed block contents"}} in mnesia_rocksdb:do_load_table/2 line 943

Do I need to rebuild the complete database from an older node with this release?

Please use 5.6.4

Will the use of 5.6.4 fix the snappy error?

Yes, 5.6.4 is 5.6.3 with one additional build flag.

I tried it, but it gets stuck at “Initializing keys manager” and doesn’t move past it.

=INFO REPORT==== 15-Jan-2021::04:26:38.010153 ===
Setup phase 200

04:26:39.223 [info] aec_db:check_db()-> ok
04:26:39.223 [info] Setup finished processing hooks (Mode=normal)...
04:26:39.277 [info] Starting reporters with [{subscribers,[{select,{[{{[ae,epoch|'_'],counter,enabled},[],['$_']},{{[ae,epoch|'_'],gauge,enabled},[],['$_']}],aec_metrics_main,[value],default,true}},{select,{[{{[ae,epoch|'_'],'$1',enabled},[{'=/=','$1',counter},{'=/=','$1',gauge}],['$_']}],aec_metrics_main,default,default,true}}]}]
04:26:41.981 [info] Starting aecore node
04:26:52.281 [info] Initializing keys manager

Ok, after a bunch of tries, it did go thru and now it is updated in 5.6.4

Welp, it only took 6 days for my node to finally be updated (partially my bad) but 5.6.3 did not help.

Oh, but I had to use master, since latest ( which points to v5.6.4 right now ) was the one that did not go pass the key part. https://hub.docker.com/layers/aeternity/aeternity/master/images/sha256-2805e212e3fc40b51064a9a74eb0b7110bbd10f255ac3e8b032ae9aa51842d31

1 Like