-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
debug_traceBlockByHash inconsistently returning nonce too high #9635
Comments
come across the same
|
I guess this will help (it will return error that block is currently non-canonical): #9616 |
It will take me a few days to have this tested properly as it is kinda hard to reproduce. Not sure why a restart solves the problem for the given block/tx, but I believe it's safe to have this issue closed. I'll try running the devel version to see how it behaves, if I encounter the problem again I can ask to reopen the issue. Edit: I couldn't test devel due to the issue #9625. Once it has been fixed, I can give it a try |
Please re-open the issue if it still happens with v2.59.2 or later. |
System information
Erigon version:
./erigon --version
erigon version 2.58.1-f12e451c
OS & Version: Windows/Linux/OSX
Amazon Linux 2023
Commit hash: f12e451
Erigon Command (with flags/config):
Consensus Layer:
Caplin
Chain/Network:
Ethereum Mainnet
Expected behaviour
This instance is an archival node synced from scratch.
We're "indexing" some information from the chain, and I call many
{ "id": 1, "jsonrpc": "2.0", "method": "debug_traceBlockByHash", "params": [ "<tx>", { "timeout": null, "tracer": "callTracer" } ] }
to retrieve the needed information.
I'd expect it to always return the needed trace calls.
Actual behaviour
Sometimes it returns for example
Once I restart my erigon node, the call starts returning the correct response.
Steps to reproduce the behaviour
Hard to say how to consistently reproduce this as it seems to be happening randomly.
The text was updated successfully, but these errors were encountered: