-
Notifications
You must be signed in to change notification settings - Fork 130
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
Syncing stuck at the SafeHead #123
Comments
It's still synced to head on my node. Can you check version of your node in docker-compose.yml?
It should returns op-node version 1.5.0 op-geth:
image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101305.3
restart: unless-stopped
stop_grace_period: 5m
entrypoint: /scripts/start-op-geth.sh
env_file:
- ./envs/${NETWORK_NAME}/op-geth.env
- .env
volumes:
- ./envs/${NETWORK_NAME}/config:/chainconfig
- ./scripts/:/scripts
- shared:/shared
- op_geth:/geth
ports:
- ${PORT__OP_GETH_HTTP:-9993}:8545
- ${PORT__OP_GETH_WS:-9994}:8546
op-node:
image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.5.0
restart: unless-stopped
stop_grace_period: 5m
entrypoint: /scripts/start-op-node.sh
env_file:
- ./envs/${NETWORK_NAME}/op-node.env
- .env
volumes:
- ./envs/${NETWORK_NAME}/config:/chainconfig
- ./scripts/:/scripts
- shared:/shared
ports:
- ${PORT__OP_NODE_P2P:-9003}:9003/udp
- ${PORT__OP_NODE_P2P:-9003}:9003/tcp |
the op-node is 1.5 i do fix some of the init-bedrock from saving the tar then extract to the stream extraction i don't think this make the problem because the node can run using the bedrock op-geth:
image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101305.3
restart: unless-stopped
stop_grace_period: 5m
entrypoint: /scripts/start-op-geth.sh
env_file:
- ./envs/${NETWORK_NAME}/op-geth.env
- .env
volumes:
- ./envs/${NETWORK_NAME}/config:/chainconfig
- ./scripts/:/scripts
- shared:/shared
- op_geth:/geth
ports:
- ${PORT__OP_GETH_HTTP:-9993}:8545
- ${PORT__OP_GETH_WS:-9994}:8546
op-node:
image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.5.0
restart: unless-stopped
stop_grace_period: 5m
entrypoint: /scripts/start-op-node.sh
env_file:
- ./envs/${NETWORK_NAME}/op-node.env
- .env
volumes:
- ./envs/${NETWORK_NAME}/config:/chainconfig
- ./scripts/:/scripts
- shared:/shared
ports:
- ${PORT__OP_NODE_P2P:-9003}:9003/udp
- ${PORT__OP_NODE_P2P:-9003}:9003/tcp |
Maybe fixed in v1.5.1 https://github.com/ethereum-optimism/optimism/releases/tag/v1.5.1 ethereum-optimism/optimism#9417 I have upgraded the latest code to v1.5.1 let's pull, rebuild and restart |
from the healthcheck its can see that the node is behind but its not syncing further more than the Safehead (checking from grafana)
and checking from the healthcheck its syncing just reach the minBlocknumber
healthcheck-1 | {"level":30,"time":1707811268639,"targetHeight":115990268,"referenceHeight":116106245,"heightDifference":115977,"minBlockNumber":115990268,"msg":"latest block heights"}
so its make the node far behind , is it have any thing that can help ?
The text was updated successfully, but these errors were encountered: