-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
The "BAD BLOCK" log is output every few minutes. #2522
Comments
Hi Team, |
Same here. The last versions are buggy like a hell. |
t=2024-06-20T12:39:42+0000 lvl=warn msg="Inserted known block" number=39777496 hash=0x90ddb49a6c82cc2cdac268b1753fd3dac692ac19cd4379c1fd5f4646abb0eb3d uncles=0 txs=18 |
It is caused by bad Erigon clients, many Erigon nodes have not upgraded to the latest release yet and they forwarded these bad blocks, try the following steps may help( 1.update your config.toml to add this option:
2.restart your node, then your nodes will reject connections from nodes named with "erigon/v1.2.5*" |
For example, this BAD BLOCK has the same block hash as the block information on BSCScan.
https://bscscan.com/block/39772307 Does this mean that BSCScan is correct in BAD BLOCK? |
Why is the block with a given hash considered bad, but successfully imported right after? |
@fatminer @ngotchac well, the block hash is ok, but the block body has been polluted... |
I tried this but didn't help for me kindly give the solution |
we have a hot fix PR: #2525, you may try the latest develop. |
thanks! |
System information
Geth version:
geth version
Geth
Version: 1.4.8
Git Commit: f5ba30e
Architecture: amd64
Go Version: go1.21.9
Operating System: linux
GOPATH=
GOROOT=/usr/local/go
OS & Version: Windows/Linux/OSX
Linux 5.15.0-1036-aws #40~20.04.1-Ubuntu SMP Mon Apr 24 00:21:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Expected behaviour
Do not output logs indicating bad blocks if the blocks are valid.
Actual behaviour
The "BAD BLOCK" log is output every few minutes.
However, when I make a "getBlockByNumber" request for the corresponding block, the response comes back without any problems.
For example, the bad blocks in the following log can be seen in Explorer.
I'm confused because they are bad block but also valid block.
t=2024-06-20T08:13:45+0000 lvl=error msg="\n########## BAD BLOCK #########\nBlock: 39772307 (0x24f665aefa6a7266438a4a51a2ef56c95b0801a20931572e47f66a55ba70fae5)\nMiner: 0x75B851a27D7101438F45fce31816501193239A83\nError: missing withdrawals in block body\nPlatform: geth (devel) go1.21.9 amd64 linux\nVCS: f5ba30e-\nChain config: ¶ms.ChainConfig{ChainID:56, HomesteadBlock:0, DAOForkBlock:, DAOForkSupport:false, EIP150Block:0, EIP155Block:0, EIP158Block:0, ByzantiumBlock:0, ConstantinopleBlock:0, PetersburgBlock:0, IstanbulBlock:0, MuirGlacierBlock:0, BerlinBlock:31302048, YoloV3Block:, CatalystBlock:, LondonBlock:31302048, ArrowGlacierBlock:, GrayGlacierBlock:, MergeNetsplitBlock:, ShanghaiTime:(*uint64)(0xc000131f28), KeplerTime:(*uint64)(0xc000131f30), FeynmanTime:(*uint64)(0xc000131f38), FeynmanFixTime:(*uint64)(0xc000131f40), CancunTime:(*uint64)(0xc000131f48), HaberTime:(*uint64)(0xc000131f50), PragueTime:(*uint64)(nil), VerkleTime:(*uint64)(nil), TerminalTotalDifficulty:, TerminalTotalDifficultyPassed:false, RamanujanBlock:0, NielsBlock:0, MirrorSyncBlock:5184000, BrunoBlock:13082000, EulerBlock:18907621, GibbsBlock:23846001, NanoBlock:21962149, MoranBlock:22107423, PlanckBlock:27281024, LubanBlock:29020050, PlatoBlock:30720096, HertzBlock:31302048, HertzfixBlock:34140700, Ethash:(*params.EthashConfig)(nil), Clique:(*params.CliqueConfig)(nil), Parlia:(*params.ParliaConfig)(0x46fbd30)}\nReceipts: \n##############################\n"
This seems to happen every time this validator generates a block.
0x75B851a27D7101438F45fce31816501193239A83
Steps to reproduce the behaviour
Occurs if it is running
The text was updated successfully, but these errors were encountered: