-
Notifications
You must be signed in to change notification settings - Fork 45
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
v0.4.2 does not sync from scratch #117
Comments
@astudnev Hello, could you provide the startup parameters for op-node and op-geth for easier problem localization? |
op geth
op node
Backtrace
|
I added logs for comparison at #118 |
I also tried set
but that did not change anything |
@astudnev Hello, can you provide longer logs for op-node to help troubleshoot? The current logs are not sufficient for identifying the issue. |
@astudnev Hello, the issue has been fixed, please try again. |
Yes, it started to sync, but from the 1st block ... now it is on 13M - is it expected behavior?
|
@astudnev Yes, this is the expected behavior if you have configured SyncMode = "full". |
looks good, thank you! |
System information
Network:
mainnet
if you are running a local node, please provide the following information:
op-node version:
0.4.2
op-geth version:
0.4.2
OS & Version: Linux
Expected behaviour
v0.4.2 installed and run in snap or full sync with empty state
Actual behaviour
If node is updated with exisitng state database from 0.3.1 to 0.4.2, it runs and sync OK
If it is installed with empty state, it never reaches to the expected
when i downgraded, is starts syncing headers
Steps to reproduce the behaviour
Install v0.4.2 geth and bnbnode on new host
The text was updated successfully, but these errors were encountered: