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
After upgrading from v1.13.15 to v1.14.5 (the node uptime was 30 days), there seem to be some missing block hash to block number links.
The issue appeared by running a simple eth_getLogs query, which returned the error: "block body not found".
After some digging, I found out that this was caused by some missing block hash to block number links:
$> seq 20233380 1 20233399 | xargs -I% -P32 bash -c 'cast logs -j --from-block % --to-block % >/dev/null || echo %'
Error:
server returned an error response: error code -32000: block body not found
20233388
Error:
server returned an error response: error code -32000: block body not found
20233389
Error:
server returned an error response: error code -32000: block body not found
20233390
System information
On Linux w/ prysm as the beacon node.
After upgrading from v1.13.15 to v1.14.5 (the node uptime was 30 days), there seem to be some missing block hash to block number links.
The issue appeared by running a simple
eth_getLogs
query, which returned the error:"block body not found"
.After some digging, I found out that this was caused by some missing block hash to block number links:
This failed as well:
while
works.
I wrote this simple
geth db
subcommand:to check for missing links, and the 3 block numbers were reported as problematic.
We can see in the logs:
Rewound to block with state number=20,233,387
after restart, which is the last valid block post-restart before the 3 missing linksLatest filled block is not available
errorLogs
The text was updated successfully, but these errors were encountered: