Closed HarukiMcCree closed 1 month ago
We suspect it is caused by the large amount of data, which leads to degraded performance of geth. If this user encounters the same issue again, we suggest that you save all the op-geth and op-node logs during the stuck period. Most likely, the error "Database compacting, degraded performance database=/data/geth/chaindata" can also be seen in the op-geth logs.
You can find more information "Data compacting" here. https://docs.bnbchain.org/opbnb-docs/docs/tutorials/running-a-local-node/
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.
The issue is closed due to long inactivity. You can reopen it for further questions or comments.
System information
Expected behaviour
Op-geth importing blocks
Actual behaviour
Op-geth does not import blocks, even after a long time (about a week). Op-geth logs:
Op-node logs:
Op-geth logs after Op-node done catching up:
Yeah, logs are taken at different time periods, but it doesn't matter IMHO Also we tried launching op-geth with different arguments and different snapshots - and it didn't resolve the issue.
Steps to reproduce the behaviour
Download and unpack snapshot archive into datadir
Start op-geth with args:
Start op-node with args: