[Node Operator Question] op-geth not syncing post upgrade, missed hardfork op-geth + op-node updating #191
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue DescriptionWe missed op-geth + op-node upgrade before hardfork, and now we tried to upgrade them to latest version but they can not sync. Do you know how can we fix the above in order to start sync again? Protocol Descriptionop-geth v1.101305.0 Node Logst=2024-01-14T10:26:36+0000 lvl=warn msg="failed to notify engine driver of L1 head change" err="context deadline exceeded" Additional InformationNo response FeedbackNo response |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 1 reply
-
|
Having the exact same issue.... Been in this state for over 24 hours. |
Beta Was this translation helpful? Give feedback.
-
|
I think this may have been answered here: |
Beta Was this translation helpful? Give feedback.
-
|
Yeah this is right, thank you for pointing to this solution. I'm collecting feedback on how we can improve network upgrade comms, so please let us know how we can improve: #184. |
Beta Was this translation helpful? Give feedback.
-
|
Error seems to indicate that your Op-Geth has stopped running. If you need re-syning the link mentioned above provides resources for snapshot data. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @eldimious, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community. |
Beta Was this translation helpful? Give feedback.
-
|
@ottomakan @sbvegan thanks for the help, i have downloaded snapshot from above link and replaced current data with snapshot's data. For some reason syncing is too slow |
Beta Was this translation helpful? Give feedback.
-
|
Mine stopped syncing at block height
114696811. Is there something else I need to do for canyon upgrade to get
past this ?
…On Tue, Jan 16, 2024 at 23:30 Dimos Botsaris ***@***.***> wrote:
@ottomakan <https://github.com/ottomakan> @sbvegan
<https://github.com/sbvegan> thanks for the help, i have downloaded
snapshot from above link and replaced current data with snapshot's data.
For some reason syncing is too slow
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3EZSN7GI4SMUT7XQKXH4GDYO542FAVCNFSM6AAAAABBZ742NGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCNJTGEYTE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I have upgraded the op-geth + op-node imgs:
And started sync from snapshot. I have not changed any flag on op-geth + op-node. How do flags look like to your setup? |
Beta Was this translation helpful? Give feedback.
-
|
I did the same. No other changes. I think there may be other flags
necessary to get past this block height
…On Tue, Jan 16, 2024 at 23:42 Dimos Botsaris ***@***.***> wrote:
I have upgraded the op-geth + op-node imgs:
- image:
us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101305.0
- image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.4.2
And started sync from snapshot. I have not changed any flag on op-geth +
op-node. How do flags look like to your setup?
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3EZSN2OMMVOV2SKZMSYPMTYO56HZAVCNFSM6AAAAABBZ742NGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCNJTGIZDA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I’ll compare with mine in athe morning; 8 hours from now. Thanks for
sharing.
…On Wed, Jan 17, 2024 at 00:04 Dimos Botsaris ***@***.***> wrote:
For op-geth my flags are:
--datadir="$BEDROCK_DATADIR" \
--http \
--http.corsdomain="*" \
--http.vhosts="*" \
--http.addr=0.0.0.0 \
--http.port=8545 \
--http.api=web3,debug,eth,txpool,net,engine \
--ws \
--ws.addr=0.0.0.0 \
--ws.port=8546 \
--ws.origins="*" \
--ws.api=debug,eth,txpool,net,engine,web3 \
--syncmode=full \
--gcmode="$NODE_TYPE" \
--nodiscover \
--maxpeers=0 \
--networkid=420 \
--authrpc.vhosts="*" \
--authrpc.addr=0.0.0.0 \
--authrpc.port=8991 \
--authrpc.jwtsecret=/shared/jwt.txt \
--rollup.sequencerhttp="$BEDROCK_SEQUENCER_HTTP" \
--rollup.disabletxpoolgossip=true \
--rollup.historicalrpc=http://l2geth:8545 \
--discovery.port=30307``` and op-node: ```js
--l1=$OP_NODE__RPC_ENDPOINT \
--l2=http://op-geth:8991 \
--network=$NETWORK_NAME \
--rpc.addr=127.0.0.1 \
--rpc.port=9545 \
--l2.jwt-secret=/shared/jwt.txt \
--l1.trustrpc \
--l1.rpckind=$OP_NODE__RPC_TYPE \
--metrics.enabled \
--metrics.addr=0.0.0.0 \
--metrics.port=7300 \
--p2p.listen.tcp=9223 \
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3EZSNYCZU6Y3QSZ5EQHGP3YO6AYXAVCNFSM6AAAAABBZ742NGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCNJTGM3TC>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
I think this may have been answered here:
#183