-
Notifications
You must be signed in to change notification settings - Fork 152
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
Cannot run trace.block() on block 2396379 on archival node #412
Comments
Hello @afmsavage. The issue with this block is that the tracer timeouts after 30seconds (default). This issue came back twice (once to myself internally) and we will have to consider giving back a better error, but before doing that we have to check if it breaks existing functionalities on services using this API. |
Just tried with
|
Even with disabling some parts of the trace it is still not enough to get a return
|
hmm, error here is different. Can you try running this command from within the node using geth's console? edit: I think the issue here might be that web3.js in browser has a timeout at 50s. Can you try same call using cURL? |
Those were directly on the node in the Javascript console. |
Can you please run this in console |
Got this error.
When calling it via
I set verbosity to 5 and the trace verbosity to 6. Here's more logging from another run that failed https://gist.github.com/afmsavage/1f832167c44011edf0932bc215d5615e |
I have been following this Issue on the Ethereum Geth repo ethereum/go-ethereum#23552. Similar issue I think. |
I think I can handle the panic (thx for the catch), but this will return the actual error and not the trace. Can you share your system stats, I care mostly for the size of your RAM. |
System has 32GB RAM.
I did notice one thing that is similar to an issue we were seeing on a Ethereum Contract Creation out of gas I cannot run a
|
Thanks @afmsavage. I can't reproduce this one, so I just check the code to find anything that can cause it. I will update you once I find something that triggers my attention. |
Looks like Geth devs have decided to disable returnData and memory by default in this pR ethereum/go-ethereum#23558 |
Thanks for sharing this @afmsavage. A nice heads up. Though this has been merged at geth 10 days ago and hasn't reached core-geth yet. @meowsbits @iquidus: just a heads up |
@afmsavage can you please try running the same using #418 and let me know of the error returned? Thanks |
System information
Geth version:
CoreGeth/v1.12.1-stable-04d026e2
OS & Version: alpine:latest image
Commit hash : (if
develop
)Expected behaviour
A successful trace of this block.
Actual behaviour
A web3js error:
Steps to reproduce the behaviour
Get a Ethereum Classic Mainnet archival node fully synced. Will include my run command below as well. In the javascript console, run
trace.block('2396379')
I have tested this on two seperate ETHClassic archival nodes as well.
Run Command
Backtrace
When submitting logs: please submit them as text and not screenshots.
The text was updated successfully, but these errors were encountered: