Open Eric-Showers opened 4 years ago
Hello!
Which version of bnbchaiind
did you use?
bnbchaind version
Binance Chain Release: v0.8.0;Binance Chain Commit: 422f0a96; Cosmos Release: v0.25.0-binance.23; Tendermint Release: v0.32.3-binance.3;
@Eric-Showers Have you verify if app.toml
file is the latest?
Yes sir - my app.toml
file is identical to the one found here
@Eric-Showers, please verify the sha256sum: 194cbad7e1adcaafc16df94576f0a3b4a26245e4019cef93c51a3183bef71d73
Okay I just completed a sha256 hash of the compressed snapshot and it matches that checksum
I confirm that the issue still presents. I downloaded Latest snapshot of February 1st and tried to sync from it on linux server. I used the latest version of the binary for linux - 0.8.2
.
:~/Binance/node-binary/fullnode/prod/0.8.2/linux# uname -a
Linux server 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 GNU/Linux
But the node crashed.
Can someone help me @huangsuyu ? I want to run an archive node but don't want to wait until the sync from scratch will finish, just need to sync from a snapshot.
Any updates on this? @huangsuyu Why does binance actually make the snapshots if they are useless as far as node can sync from them?
@alexqrid Checking! i will come back to you asap
Okay I just completed a sha256 hash of the compressed snapshot and it matches that checksum
can you check if you set open file limit to 65535?
can you check if you set open file limit to 65535?
Yes I did. Open file limit was set to 65535. The problem is with wrong block hash as you can see from the logs.
Steps followed:
1) Installed node on Ubuntu 18.04.3 using this article 2) Downloaded most recent snapshot from this article and followed instructions 3) Modified
config.toml
state_sync_reactor = false
state_sync_height = -1
4) Ran
bnbchaind start
, which produced this error:panic: Failed to process committed block (112397623:6EA3AE907079229A36C4F8F12E00FB682BEF23A6349419722C76FA14F13EC329): Wrong Block.Header.AppHash. Expected F9F03780A35803BFE10F60A5814D48ED059016032CD04075D44BA3233B559D98, got ACE158FBC230B0897622D8D8913FC538F2B73A51B9C9627C4A66D5F081AD7C84
goroutine 58419 [running]: github.com/tendermint/tendermint/blockchain/v0.(*BlockchainReactor).poolRoutine(0xc00b0469c0) /root/bnbchain/pkg/mod/github.com/binance-chain/bnc-tendermint@v0.32.3-binance.3/blockchain/v0/reactor.go:404 +0x1c70 created by github.com/tendermint/tendermint/blockchain/v0.(*BlockchainReactor).OnStart /root/bnbchain/pkg/mod/github.com/binance-chain/bnc-tendermint@v0.32.3-binance.3/blockchain/v0/reactor.go:127 +0x84
5) Attempted running again, same error:
ERROR: error during handshake: error on replay: Wrong Block.Header.AppHash. Expected F9F03780A35803BFE10F60A5814D48ED059016032CD04075D44BA3233B559D98, got ACE158FBC230B0897622D8D8913FC538F2B73A51B9C9627C4A66D5F081AD7C84
Was it a mistake to turn off state sync? I need this node to have access to all historical blocks so I assumed that fast sync would be required.