-
Notifications
You must be signed in to change notification settings - Fork 17
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
forkChoiceUpdated timeout #229
Comments
We have the very same issue for base-mainnet chain |
@janzhanal Thanks for summarizing the issue! the Are you syncing from one of our snapshots on the https://snapshot.testinprod.io/#op-sepolia-archive-node? Also, could you please set |
Hello, yes we did use the snapshot.. The question is if just extending this timeout won't help. Even though @cshintov wrote he did build the app with longer timeout and it didn't help... |
@janzhanal That timeout is actually a part of optimism spec and op-node will also err if the timeout exceeds 5 seconds, so extending on erigon side might not really help. |
So bit more logs here:
|
@janzhanal Okay, based on the logs, i see two things
However, if you have a snsapshot you are syncing from, it might be better to just use consens-layer syncmode to get the nodes going. Could you remove the |
@cshintov That log doesn't show any information about the block building itself. Can you provide a log txt file for over a longer period? |
Hello @cshintov , are there any updates to this issue? |
System information
Erigon version:
./erigon --version
erigon version 0.07.2-unstable
OS & Version:
Linux , 5.15.0-122-generic #132~20.04.1-Ubuntu
Commit hash:
812c1f7
Erigon Command (with flags/config):
Consensus Layer:
op-node
Consensus Layer Command (with flags/config):
Chain/Network:
op-mainnet
Expected behaviour
Node to sync to the tip
Actual behaviour
Node doing rollup and starts syncing from snapshot
Steps to reproduce the behaviour
Start the node
Backtrace
(from new to old)
The text was updated successfully, but these errors were encountered: