Skip to content
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected #87

Closed
prettyCoders opened this issue Jul 29, 2019 · 17 comments

Comments

@prettyCoders
Copy link

image

@chainwhisper
Copy link
Contributor

Hello, @prettyCoders

Can you provide more information please?

Which env: testnet or mainnet?
Which system?
Which version of bnbchaind?
Have you upgraded your node?
If so, did you replace your config files?

Thanks!

@prettyCoders
Copy link
Author

mainnet Ubuntu16.04 0.5.9
It`s new node

@chainwhisper
Copy link
Contributor

mainnet Ubuntu16.04 0.5.9
It`s new node

please upgrade to v0.6.0

@prettyCoders
Copy link
Author

prettyCoders commented Jul 29, 2019 via email

@AllBeaver
Copy link

I have the exact same error on the same block, v0.6.0 mainnet

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 27EAAF94E6D1D91453E1EE01980EC97CA198ADFD585D65631858D5417896B3FA, got 043B82711934F40AC0FA9226A166368FDC486D05C3DF9C18
56165890A8BD6A54

@chainwhisper
Copy link
Contributor

I have the exact same error on the same block, v0.6.0 mainnet

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 27EAAF94E6D1D91453E1EE01980EC97CA198ADFD585D65631858D5417896B3FA, got 043B82711934F40AC0FA9226A166368FDC486D05C3DF9C18
56165890A8BD6A54

did you upgrade your fullnode?

if so, did you replace the config files?

@momaer
Copy link

momaer commented Aug 13, 2019

I have the exact same error.
os: ubuntu 16.04.4 LTS
version: 0.6.1
replaced the config files

when sync done , I press ctrl + c , then run the command bnbchaind start --home /opt/bnb again , it print errors:
ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 9B3777FD460822F10E9BF06888DC02B6D2535D7D72965C9B0E9AF11AB2BC0901, got 974B56A413D30A923B80C8AEA337B028086A8EFE149934C3ACD176C81FE333D2

What should I do?

@chainwhisper
Copy link
Contributor

Hello, @momaer

Did you stop your node and sync again?

@momaer
Copy link

momaer commented Aug 14, 2019

Hello, @momaer

Did you stop your node and sync again?

yes, I stoped and sync again, and it works. interesting.

@XieWeiZM
Copy link

image
@huangsuyu

@mutianqi
Copy link

I have the exact same error.
os: ubuntu 16.04.4 LTS
version: 0.6.1

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 877BD40C8068863FB000EDC917A0E2C3B38F14F86F610129F6946344AB061F94, got 588061D18993C67A8D4070C564097636895090B8832BE87455D70B13D377933D

The program dies when this error occurs.
@huangsuyu

@chainwhisper
Copy link
Contributor

I have the exact same error.
os: ubuntu 16.04.4 LTS
version: 0.6.1

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 877BD40C8068863FB000EDC917A0E2C3B38F14F86F610129F6946344AB061F94, got 588061D18993C67A8D4070C564097636895090B8832BE87455D70B13D377933D

The program dies when this error occurs.
@huangsuyu

please upgrade to v0.6.2 and start again.

@mutianqi
Copy link

image

I have upgraded v0.6.2, but there is still the same error

@huangsuyu

@chews
Copy link

chews commented Nov 4, 2019

I'm getting this on testnet, running 0.6.2 with a config from 0.6.2 it seems to work fine for a while, when it fails I cannot re-join the netowork.

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 1C961B3BDC13397418AE93EBD74A2147CE5CC375934F41432F60FA540929F22D, got F7600CE80FF71D09A77B357273C2FE90E5D7CE7A58FE68852435FA0090D76D36

I've tried state_recover to an earlier block to restart it but then I get
failed to get rootMultiStore: no data

@chainwhisper
Copy link
Contributor

I'm getting this on testnet, running 0.6.2 with a config from 0.6.2 it seems to work fine for a while, when it fails I cannot re-join the netowork.

ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 1C961B3BDC13397418AE93EBD74A2147CE5CC375934F41432F60FA540929F22D, got F7600CE80FF71D09A77B357273C2FE90E5D7CE7A58FE68852435FA0090D76D36

I've tried state_recover to an earlier block to restart it but then I get
failed to get rootMultiStore: no data

Hello, @chews

Can you provide the error log when your node crashed for the first time?

@katevoskresenska
Copy link

I've faced the same issue running full node on mainnet:
panic: Failed to process committed block (65991707:5332FC00BAF84E3F78436FD420C76634C34449E51853A7A5CA13AB8F7558C99D): Wrong Block.Header.AppHash. Expected 380EDC2746CA47EFBCC126A2213255629B9F4C0926FF382DD08FA8640342EC08, got 586F1E2FAB2F8C7F56ECF8536B2F1581B334CC255DD1EDD75D27342DF0F0AE0A

To resolve it, I have changed the following option from true to false in config.toml:
# If false, will not check appHash when apply block
with_app_stat = false
And restarted node in state_sync mode:
state_sync=true
state_sync_height = 0
Keep in mind that it is required to delete/rename $bnb_home/data and $bnb_home/config/priv_validator_key.json before restart (Source: https://docs.binance.org/fullnode.html)

@kenorb
Copy link

kenorb commented Nov 13, 2021

See: cosmos/cosmos-sdk#10281

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants