-
Notifications
You must be signed in to change notification settings - Fork 1.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
block not found error with debug_traceCall #5365
Comments
I'm having the same issue. |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
I assume this is still an issue |
Just ran into the same issue as well after using
|
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
. |
This is still an issue - querying blocks older than ~2 weeks results in this issue |
your --prune flags? |
Hi this is still an issue for debug_traceCallMany. |
@AskAlexSharov |
your --prune flags? |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
System information
Erigon version:
v2022.09.01
Issue
When making the following request to the node, it returns block not found:
Output is malformed JSON stating that the block cannot be found:
The node is in sync and the block does exist, I can call debug_traceBlockByNumber against this block just fine.
The text was updated successfully, but these errors were encountered: