Rejected header marked as bad hash
JB273 opened this issue · comments
Since today we are receiving this on our BSC node:
[WARN] [01-23|13:35:52.361] [downloader] Rejected header marked as bad hash=0x9734e59a71729ea44d6f1fe69ad0bc5f7d8fb5b0dedbb2cb819ea748cf32ace2 height=35495571
It does not progress after this
Also got this a bit up in the logs:
[EROR] [01-23|13:33:02.713] [9/15 IntermediateHashes] Wrong trie root of block 35495571: 0d4c0b5f50d137d56ba783dc8e2c4e608e80cbda3eaaea6f2c193cd88c03a468, expected (from header): 0850387dc495dc86d61b5d6f757ee3bf3e9132ab3c1fc2715d46bab554c836ac. Block hash: 9734e59a71729ea44d6f1fe69ad0bc5f7d8fb5b0dedbb2cb819ea748cf32ace2
Also got this a bit up in the logs:
[EROR] [01-23|13:33:02.713] [9/15 IntermediateHashes] Wrong trie root of block 35495571: 0d4c0b5f50d137d56ba783dc8e2c4e608e80cbda3eaaea6f2c193cd88c03a468, expected (from header): 0850387dc495dc86d61b5d6f757ee3bf3e9132ab3c1fc2715d46bab554c836ac. Block hash: 9734e59a71729ea44d6f1fe69ad0bc5f7d8fb5b0dedbb2cb819ea748cf32ace2
Hi, I faced this issue in the past. You should unwind node - that should help.
Have the same issue.
when this issue appeared I was on version v1.1.10
then I updated to the latest v1.1.12
when I make unwind command
integration state_stages --unwind=10000 --chain=bsc --datadir /opt/bsc
then I receive the following error:
INFO[01-23|15:26:03.128] [9/15 IntermediateHashes] Calculating Merkle root current key=e9dae3d7
INFO[01-23|15:26:19.965] [9/15 IntermediateHashes] Calculating Merkle root current key=f42f9d2f
EROR[01-23|15:26:44.477] [9/15 IntermediateHashes] wrong trie root: 370ce8693960fd86f47c882ef95e16f46165ef0dc7bc6e18bb8943b87c0c4e3b, expected (from header): c7855bbe2595ccf4bfaabd20db9618658c9ce7b9ec924bc2247a245fe3bf620f
Have the same issue. when this issue appeared I was on version v1.1.10 then I updated to the latest v1.1.12
when I make unwind command
integration state_stages --unwind=10000 --chain=bsc --datadir /opt/bscthen I receive the following error:INFO[01-23|15:26:03.128] [9/15 IntermediateHashes] Calculating Merkle root current key=e9dae3d7 INFO[01-23|15:26:19.965] [9/15 IntermediateHashes] Calculating Merkle root current key=f42f9d2f EROR[01-23|15:26:44.477] [9/15 IntermediateHashes] wrong trie root: 370ce8693960fd86f47c882ef95e16f46165ef0dc7bc6e18bb8943b87c0c4e3b, expected (from header): c7855bbe2595ccf4bfaabd20db9618658c9ce7b9ec924bc2247a245fe3bf620f
Maybe this command could help:
integration stage_headers --unwind=10000 --chain=bsc --datadir=/opt/bsc
If not, what helped me but on polygon erigon was to exec
integration stage_hash_state --chain bsc --datadir=/opt/bsc
and then to repeat unwind.
Hi there, Try integration stage_headers —reset. JFYR: #289 (comment)
Actually v1.1.10 have some bugs in system contract upgrade. It's fixed in v1.1.12. So please use the v1.1.12 for the hardfork.
Try
./build/bin/integration stage_hash_state --datadir= --reset
./build/bin/integration stage_trie --datadir= --reset
Recovering from the integration stage_headers --reset currently
If it doesn't work will those commands still help @blxdyx ?
Or will we only be able to download and start from a new snapshot?
Recovering from the
integration stage_headers --resetcurrentlyIf it doesn't work will those commands still help @blxdyx ? Or will we only be able to download and start from a new snapshot?
You could still try those command.
Recovering from the
integration stage_headers --resetcurrently
If it doesn't work will those commands still help @blxdyx ? Or will we only be able to download and start from a new snapshot?You could still try those command.
Now trying to sync again after those commands...
Actually v1.1.10 have some bugs in system contract upgrade. It's fixed in v1.1.12. So please use the v1.1.12 for the hardfork. Try ./build/bin/integration stage_hash_state --datadir= --reset ./build/bin/integration stage_trie --datadir= --reset
Running 1.1.12 already, until now no luck...
I don’t know how you can come to this state. Maybe some unwind or reset broken the data. I suggest download the new snapshot. https://github.com/bnb-chain/bsc-snapshots?tab=readme-ov-file#endpointmainnet-update-bi-weekly
Downloading now the snapshot, was unable to fix it with any of the above solutions, all ended up with the error:
Wrong trie root of block
Download the snapshot and start with a new datadir use the latest release?
Oh wait.. Only the snapshots dir? Or the whole data also (mdbx)?
I'm doing both, but if only the snapshots will be needed will be faster of course...
Using 1.1.12 the whole time already...
I mean the mdbx snapshot, the snapshots dir usually won't have some problem.
Reopen if still have some problem