[BUG]Node can't pass block nonce 10270062 about mx-chain-go

[iulianpascalau]

The error signaled when processing the block epoch = 713 shard = 1 round = 10277217 nonce = 10270063 is receipts hash missmatch.
This can be caused by a multitude of factors like bad configs, wrong binary version, an internal bug, wrong/incomplete trie state
I've emphasized the wrong or incomplete trie state because we have recently found this behavior on our nodes that was related to the closing of the node while it was doing a snapshot. If this occurs on a node with the v1.3.35 version, the snapshot is incomplete but the DB is marked as a DB with a complete snapshot and this might trigger the above error. I can not see from this log, I was wondering if the node started to work just after the epoch 714 was notarized by the metachain. This behavior would have triggered a new trie re-sync from the network.
This is the PR that contains the fix, it is still under review & heavy testing: #4281

[phanletrunghieu]

log.txt

My full node in devnet met the same problem. There're 2 suspicious log lines

error = roll back behind final header is not permitted
error = block bodies does not match

[phanletrunghieu]

This is the log file before node restarted.
https://drive.google.com/file/d/18IhXxEbw49vOycw3DFMB_3BbBeCxxzYA/view?usp=sharing

[iulianpascalau]

will take a look

[iulianpascalau]

Do we have older logs? The reason for this is that the log's oldest record started with the error block bodies does not match so we can not figure out what happened. Did you used the ./script.sh get_logs functionality?

[LucianMincu]

Hi @poussette @phanletrunghieu!

Awesome news for you! 🔥
elrond-go v1.3.36 has been released! 🚀

The release includes the fixes for the root cause of the issue from above.

Thanks for reporting it and your contribution! 🙏