Failed to share forkchoice-updated signal
Closed this issue · 6 comments
UranusLin commented
I am running simple-optimism-node on Goerli and have updated to op-node:v1.3.0, but the op-node can't sync due to the error "Failed to share forkchoice-updated signal".
The op-node logs show:
t=2023-11-15T03:49:36+0000 lvl=warn msg="Failed to share forkchoice-updated signal" state="&{HeadBlockHash:0x88776a73adfa67a147faa64bddfad8d26ce2b01d62289f68486cb2e1cac61166 SafeBlockHash:0x88776a73adfa67a147faa64bddfad8d26ce2b01d62289f68486cb2e1cac61166 FinalizedBlockHash:0x69a5a078675d93842ae0f87ec8e99a6c5f1fafd8008a4f02c9572afed8cf9738}" attr="&{Timestamp:0x6553a790 PrevRandao:0x3c6cfc1ee8795baaabdaa28e11f357ccb5ddea424c7f067999201161d791c11f SuggestedFeeRecipient:0x4200000000000000000000000000000000000011 Withdrawals:0xc004df5830 Transactions:[0x7ef90159a089966597ecc893be5da3068ba8fd9d245a3024e8f0cb674e8ba6d0e1bd912b6294deaddeaddeaddeaddeaddeaddeaddeaddead00019442000000000000000000000000000000000000158080830f424080b90104015d8eb90000000000000000000000000000000000000000000000000000000000993f0c000000000000000000000000000000000000000000000000000000006553a73c000000000000000000000000000000000000000000000000000000000000001c563f4dcc8b94305c00af2832eafc2a1c6782b9cccf08caab812e9d5fc1f029e700000000000000000000000000000000000000000000000000000000000000050000000000000000000000007431310e026b69bfc676c0013e12a1a11411eec9000000000000000000000000000000000000000000000000000000000000083400000000000000000000000000000000000000000000000000000000000f4240 0x02f903558201a482a6ec840bebc1ce840becc374835b8d80946cc89194b7864d90107e15097a93168747cef66c80b902e4b1dc65a40001460c1f89ef3f83f76c2e6b2125770c254264f3e769091a54a68f5711634600000000000000000000000000000000000000000000000000000000000096033343295aeadac584752c2ea3bc2849dc5c425d236384e5068a01b7be5f70383100000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000220000000000000000000000000000000000000000000000000000000000000028000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000ccf0a31a221f3c9b0000000000000000000000000000000000000000000000000000007b2f10996000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002cab59c005bb6d87bbfb8a575cb563472181f95bd163246ff45c2bf4c9d71d85f58c7afaef6cc1e4934623c0e73dc477374d6a6ef9952408338bf2d65ddb9143e0000000000000000000000000000000000000000000000000000000000000002781fb93b7c748b7929b27b32f6bf3dab7c9d81501b92c0c7a85b17eba7fa360d6bd4aef8f3f10aea2d12859c759a5f6516537b2e6bb6fb63f080243fb72c67c2c001a05acaf53861923847ae199e8ce19622e027d047c8c9ac0ce45e34c8dc1b3934f9a034e6dd492c60ffc13c01e28adbce6a63374499ffbdf828878c600e99ea8dccf1] NoTxPool:true GasLimit:0x2faf080}" err="Invalid parameters"
t=2023-11-15T03:49:36+0000 lvl=warn msg="Derivation process temporary error" attempts=5 err="engine stage failed: temp: temporarily cannot insert new safe block: failed to create new block via forkchoice: unrecognized rpc error: Invalid parameters"
How can I fix this? Any help is appreciated.
Chomtana commented
Can you share your (Make sure to have secret masked)
# L1 node that the op-node (Bedrock) will get chain data from
OP_NODE__RPC_ENDPOINT=
# Type of RPC that op-node is connected to, see README
OP_NODE__RPC_TYPE=basic
But it's just a warning. If it happen randomly not always it's fine.
UranusLin commented
We using
# L1 node that the op-node (Bedrock) will get chain data from
OP_NODE__RPC_ENDPOINT=[Our Ethereum Goerli fullnode]
# Type of RPC that op-node is connected to, see README
OP_NODE__RPC_TYPE=basic
It's still not syncing, should we re init data and sync from 0?
mmd-afegbua commented
I am experiencing this as well. Node is stuck and not syncing.
Chomtana commented
Hi @UranusLin @mmd-afegbua I'm forwarding this issue to ethereum-optimism/developers#88
So core dev can look into that
sbvegan commented
I've responded in that thread: ethereum-optimism/developers#88 (comment), it looks like this is due to the canyon hardfork on testnets.
This repo probably needs the configuration for Canyon and should also migrate over to OP Sepolia for testnets because OP Goerli will not be supported starting next year.