-
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
failed to get logs for block #7950923 (0xff68a7..396b6d)
on long running node
#30470
Comments
Can you please try |
Sure thing.
|
It would be helpful to see what is exactly persisted. Since it is an old block it is stored in the freezer and not kvdb. Even though we have a method debug_dbGet for reading values from the kvdb we don't have something for reading freezer values. Once we have this method we can make progress on debugging the issue. |
Ah pardon turns out we do have a method for that. Can you please try calling this? you will have to enable the debug namespace (via
This is the value I'm getting on my node:
|
I think the issue is that we might have at some point changed the way we store receipts in the database. |
These nodes have been running for quite a long time. I guess we'll need to do a resync? |
@shammahalchemy Could you please check this comment: #30470 (comment) ? |
@shammahalchemy Please run this to retrieve the raw value: curl localhost:8545 --header 'Content-Type: application/json' --data '{
"method": "debug_dbAncient",
"params": [ "receipts", 1022389 ],
"id": 1,
"jsonrpc": "2.0"
}' |
@fjl sure thing. Thank you for looking.
|
rlpdump:
Vs the correct dump:
Yeah Marius was right this is a legacy receipt type. @shammahalchemy were you using |
There is no conversion path in the code for legacy receipts anymore. So the only option is resync without ancients. |
System information
Geth version: ethereum/client-go:v1.14.5
CL client & version: prysmaticlabs/prysm-beacon-chain:v5.0.4
OS & Version: Linux
Expected behaviour
Output block logs.
Actual behaviour
Node logs output the following:
It seems to be a similar issue to this: #25809
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: