Skip to content
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

The node is always about 21620 blocks behind #127

Open
blocknodehub opened this issue Aug 20, 2024 · 0 comments
Open

The node is always about 21620 blocks behind #127

blocknodehub opened this issue Aug 20, 2024 · 0 comments

Comments

@blocknodehub
Copy link

Hello ! Since the last upgrade to the consensus layer synced version, the node has been lagging behind by about 21620 blocks.
The current node version is:
us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.7
us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101315.2
I deployed it according to the following document.
https://github.com/b2network/docs/blob/main/nodes/running_rollup_node.md
What should I do to restore the node?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant