node-binary icon indicating copy to clipboard operation
node-binary copied to clipboard

App header Mismatch

Open jseibel-circle opened this issue 4 years ago • 9 comments

ERROR: error during handshake: error on replay: Wrong Block.Header.AppHash. Expected 818A511D2C19FA4710FD566D477809FEDA86289C3A19B894AFAB65C9950E6F38, got E023C52BF275A3806088F69C336C7EC888A64271997FED1274C0CA7C6FF38C21

On the latest 8.0, everything working fine, then this happens and took down the node. We have had this happen randomly since the beginning of integrating the binance chain. Will this ever be fixed so it stops happening? It's a very annoying error that requires manual steps to fix, and it happens at least once a month. As this is a closed-source blockchain, our devs can't issue a fix for you, so your team must fix this yourselves.

jseibel-circle avatar Aug 28 '20 13:08 jseibel-circle

The height this is crashing on is 109999000 which is probably the hard fork for new consensus as it's such a round number. All of our nodes have this issue. We are going to destroy the blockchain on disk and resync above this height. This exact same issue happened on the last major release that had a consensus change. So your own release can't handle the block containing the hard fork. It's very bad that this happens and I hope you take this seriously and fix this.

jseibel-circle avatar Aug 28 '20 13:08 jseibel-circle

Have same issue. Recovering to height 109999000 doesn't help. Node is stopped and can't sync.

oggy95 avatar Aug 28 '20 14:08 oggy95

Same issue here, have tried several times with a fresh start, same errors.

cedricfung avatar Aug 28 '20 17:08 cedricfung

Hello @jseibel-circle

You need to update app.toml file and recover to 109998999 (one block before the upgrade height)

and make sure your system open-file limit is at least 1024.

https://community.binance.org/topic/3103/

chainwhisper avatar Aug 29 '20 04:08 chainwhisper

@huangsuyu yes, it's help, thank you very much.

oggy95 avatar Aug 29 '20 09:08 oggy95

I used the new app.toml and config.toml, deleted all other data, it still panics, the file limit is set to 65566.

cedricfung avatar Aug 29 '20 09:08 cedricfung

@cedricfung i replaced app.toml, config.toml and genesis.json in .bnbchaind/config/, use "state_recover 109998999 ~/.bnbchaind" and start bnbchaind and it works.

oggy95 avatar Aug 29 '20 09:08 oggy95

After that, it now produces this error https://github.com/binance-chain/node-binary/issues/243

cedricfung avatar Aug 29 '20 09:08 cedricfung

After that, it now produces this error #243

Please revert one block before restart:

The recover workflow is the following:

  1. Download the tool state-recover from node-binary repo for fixing the upgrade issue
  2. Backup your home directory Since the height of the upgrade is set to be 109,999,000, you can run the following command to recover the state to just one block before the upgrade, which is 109,998,999 :
./state_recover 109998999 <your_home_path>
  1. Restart with the version v0.8.0 of bnbchaind
bnbchaind start --home <home-path>

chainwhisper avatar Aug 30 '20 02:08 chainwhisper