-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
engine_newPayloadV3
RPC Method call
#31011
Comments
It looks like the panic is coming from your code |
Ok so that's the weird issue I am seeing. The node has been running as expected up to head for weeks on end with no crashes whatsoever. This is why I kinda have the feeling there is an issue with the async thread calling So would it be possible the thread would make the call out of scope of the normal block processing? |
Can you expand on why you think this is an issue in go-ethereum? The panic is coming from your code here: You're building a custom view of the call stack in a custom tracer. It's possible your tracer doesn't perfectly represent the true call stack. I don't see how additional calls to We'll need more information from you to diagnosis this. Are you even using the |
Ok I will gather more information on this and keep monitoring it. Thank you for your help @lightclient |
System information
Geth version:
geth version
CL client & version: e.g. lighthouse/nimbus/[email protected]
OS & Version: Linux
Commit hash : (if
develop
)Expected behaviour
RPC call should not break
geth
node running.Actual behaviour
The issue occurred on
op-sepolia
running the firehose tracer. It occurred randomly and it doesn't occur on each new block. It would break the firehose tracer if the methodengine_newPayloadV3
is called outside of the normal flow between EL <> CL.Steps to reproduce the behaviour
Kinda hard to reproduce, it occurred randomly after weeks of running a node that had run as expected.
Also, once the node is restarted, it would work as expected without any issues. A hypothesis, would be that the issue could come from https://github.com/ethereum/go-ethereum/blob/master/beacon/blsync/engineclient.go#L95-L119 where there is an async go func running.
Backtrace
Could there be any issue with the
updateLoop
which would callengine_newPayloadV3
on a fork or something which could cause the node to panic?The text was updated successfully, but these errors were encountered: