-
Notifications
You must be signed in to change notification settings - Fork 20.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequent invalid merkle state root BAD BLOCK errors on all nodes #30077
Comments
The block
And the correct one is |
As long as your chain is progressing, the issue seems that one signer is corrupted and it's trying to make bad block every time it is it's turn. You need to check that machine whether it's SSD is borked or just a db corruption (srrange). |
System information
Geth version: 1.13.15-stable
CL client & version: none, using Clique PoA
OS & Version: Linux
Commit hash: c5ba367
Expected behaviour
Applying proposed blocks containing transactions should result in the same state root across synchronized validators.
Actual behaviour
A simple token send transaction results in an error:
invalid merkle root (remote: 020c9b1592689f364f784224287e7b7844fffa4efd697798ddce55897fe3618d local: c5efce337aa62af3fe0dca863454b3cd183dd2ea73f0c1e85e2dbf065ac432cb)
Steps to reproduce the behaviour
I have deployed a PoA chain using the last PoA-supported version of geth. The network configuration is three fully-connected mining node and one non-mining RPC node on VMs in Google Cloud, each running geth via docker compose.
Some details:
genesis.json
geth options:
The full deployment and configuration is public and visible here (satori).
Logs
Validator 1
Validator 2
Validator 3
Console
On Validator 1:
The text was updated successfully, but these errors were encountered: