-
Notifications
You must be signed in to change notification settings - Fork 116
ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected #87
Comments
Hello, @prettyCoders Can you provide more information please? Which env: testnet or mainnet? Thanks! |
mainnet Ubuntu16.04 0.5.9 |
please upgrade to v0.6.0 |
OK
发自我的iPhone
…------------------ Original ------------------
From: huangsuyu <[email protected]>
Date: 周一,7月 29,2019 10:29
To: binance-chain/node-binary <[email protected]>
Cc: prettyCoders <[email protected]>, Mention <[email protected]>
Subject: Re: [binance-chain/node-binary] ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected (#87)
mainnet Ubuntu16.04 0.5.9
It`s new node
please upgrade to v0.6.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
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 |
did you upgrade your fullnode? if so, did you replace the config files? |
I have the exact same error. when sync done , I press ctrl + c , then run the command bnbchaind start --home /opt/bnb again , it print errors: What should I do? |
Hello, @momaer Did you stop your node and sync again? |
yes, I stoped and sync again, and it works. interesting. |
I have the exact same error. ERROR: Error during handshake: Error on replay: Wrong Block.Header.AppHash. Expected 877BD40C8068863FB000EDC917A0E2C3B38F14F86F610129F6946344AB061F94, got 588061D18993C67A8D4070C564097636895090B8832BE87455D70B13D377933D The program dies when this error occurs. |
please upgrade to |
I have upgraded v0.6.2, but there is still the same error |
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.
I've tried state_recover to an earlier block to restart it but then I get |
Hello, @chews Can you provide the error log when your node crashed for the first time? |
I've faced the same issue running full node on mainnet: To resolve it, I have changed the following option from |
The text was updated successfully, but these errors were encountered: