You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Restarting standalone Silkworm at commit20ec45ad1a3e550afbbe05a63a5cc350d8374bbd after fixing #2349, an invalid block error pops up while doing the initial cleanup forward cycle:
...
INFO [09-12|07:00:54.787 UTC] Total reopened bundles: 68 snapshots: 204 indexes: 272 max block available: 20'461'999
INFO [09-12|07:00:54.787 UTC] SnapshotSync: database Senders stage progress updated [20'461'999]
INFO [09-12|07:00:54.787 UTC] Revalidate canonical chain up to number=20'726'754 hash=3b79e0b2446357490a79240d017133396dd96e503c070dfcabe6ef57a2f58070
INFO [09-12|07:00:54.787 UTC] sentry Sentry received initial status message
INFO [09-12|07:00:54.787 UTC] ExecutionPipeline Forward start
INFO [09-12|07:00:54.787 UTC] [4/12 Senders] op=Forward from=20461999 to=20726754 span=264755 max_batch_size=139810
...
INFO [09-12|07:03:16.171 UTC] [4/12 Senders] op=Forward done=2m 21s
INFO [09-12|07:03:16.171 UTC] [5/12 Execution] op=Forward from=20460999 to=20726754 span=265755
...
INFO [09-12|07:42:46.177 UTC] [5/12 Execution] block=20581339 blocks/s=65 txns/s=9784 Mgas/s=992
INFO [09-12|07:42:48.147 UTC] sync::SentryClient Peer 8df34663c567f2dd0d8923b5e08459b243d17d80 connected, active 72, info: client_id=Nethermind/v1.28.0+9c4816c2/linux-x64/dotnet8.0.8 / enode_url=enode://8df34663c567f2dd0d8923b5e08459b243d17d80f66ecc5b0ba56947131ee32e2c526282ad64c7f8ab32b6ddd38a155b849600dd09e0c4b15f28578e83913e84@91.187.65.237:30404
INFO [09-12|07:42:48.546 UTC] Flushed state size=24.03 MB in=1.225s
WARN [09-12|07:42:48.561 UTC] [5/12 Execution] block=20581423 hash=0x3214e0f942973e0f0b863d8fe571aaaa25018b1fafbe6b0ce36a7ac7e2077bd5 error=kInsufficientFunds
ERROR [09-12|07:42:48.566 UTC] [5/12 Execution] function=forward exception=kInvalidBlock
ERROR [09-12|07:42:48.566 UTC] [5/12 Execution] op=Forward returned=kInvalidBlock
ERROR [09-12|07:42:48.566 UTC] ExecPipeline Forward interrupted due to stage Execution failure
INFO [09-12|07:42:48.566 UTC] MainChain::collect_bad_headers bad_count=145'332 skip=1
INFO [09-12|07:42:48.566 UTC] ExecutionPipeline Unwind start
INFO [09-12|07:42:48.566 UTC] [9/12 Senders] op=Unwind from=20726754 to=20581422 span=145332
INFO [09-12|07:42:49.608 UTC] sync::SentryClient Peer f50ad13decd40b434b1173f414143a88974718b3 disconnected, active 71, info: -info-not-found-
INFO [09-12|07:42:49.656 UTC] sync::SentryClient Peer dd9f2b398c4c27658d6e0fa24903b526f7cd4d39 disconnected, active 70, info: -info-not-found-
INFO [09-12|07:42:52.127 UTC] sync::SentryClient Peer 66abe0dd0a35cac43ab8b6affab328b02f555d88 connected, active 71, info: client_id=Nethermind/v1.27.1+d2d5d4ae/linux-x64/dotnet8.0.7 / enode_url=enode://66abe0dd0a35cac43ab8b6affab328b02f555d884ba3c2c50374baf6b7603bcc6cd09a8ec1161bad26e77b96dee864bc990e0de0a0889ea6ff6f8533faf96f92@108.217.32.157:30303
INFO [09-12|07:42:54.861 UTC] [9/12 Senders] op=Unwind done=6.295s
INFO [09-12|07:42:54.861 UTC] [10/12 Bodies] op=Unwind from=20726754 to=20581422 span=145332
INFO [09-12|07:42:54.861 UTC] [11/12 BlockHashes] op=Unwind from=20726754 to=20581422 span=145332
INFO [09-12|07:42:54.862 UTC] [12/12 Headers] op=Unwind from=20726754 to=20581422 span=145332
INFO [09-12|07:42:54.862 UTC] ExecutionPipeline Unwind done
INFO [09-12|07:42:54.943 UTC] PoSSync: Waiting for blocks... from=20'726'754
...
Block hash 0x3214e0f942973e0f0b863d8fe571aaaa25018b1fafbe6b0ce36a7ac7e2077bd5 written in the log in incorrect for block 20581423, see here.
This is the result looking at the content of Silkworm database:
Fixes#2359
This PR restores in stage Execution the invalid block handling logic removed in #1511
Also fixes the invalid block reference lifetime issue causing an incorrect block hash to be stored as bad block hash in SyncContext and displayed into the warning log, as described in #2358
The root cause of this problem turned out to be an invalid set of block snapshots appeared on erigon-snapshot: notably, some body segment files contained misaligned data wrt the related transaction segment files.
Restarting standalone Silkworm at commit20ec45ad1a3e550afbbe05a63a5cc350d8374bbd after fixing #2349, an invalid block error pops up while doing the initial cleanup forward cycle:
Block hash
0x3214e0f942973e0f0b863d8fe571aaaa25018b1fafbe6b0ce36a7ac7e2077bd5
written in the log in incorrect for block20581423
, see here.This is the result looking at the content of Silkworm database:
Block hash
c49d87a766d3a4b4360ca01ced7abeb8d32ddd2f0f683fae0ab789668b6faa0e
present in the db is correct for block20581423
.sw_invalid_block.log
The text was updated successfully, but these errors were encountered: