Closed blakelukas closed 1 year ago
Hi there, Can you share some more logs of op-geth
(around 100+ lines of logs) and also the output of following command:
curl -X POST -H "Content-Type: application/json" --data \ '{"jsonrpc":"2.0","method":"optimism_syncStatus","params":[],"id":1}' \ http://localhost:8546 | jq .
And,
L1_RPC
public RPC url you used? (Can you try changing to rpc another one from the list here: https://www.bnbchainlist.org/ once)Hello! Yes, I've attached a file with the logs. Also, the cURL sample inside the container didn't work as expected, and the same goes for the original documentation. So, I don't have complete information yet. Maybe I mixed up the port or something else. It responds fine to standard requests.
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32601,
"message": "the method optimism_syncStatus does not exist/is not available"
}
}
Hi there, Nice catch. It could be due to port mismatch as well. Please use same --ws.port
as --http.port
in op-geth
startup command. I can see that you have different port over here:
Recommended is this:
I would recommend to cross-verify the commands being used as per here: https://docs.bnbchain.org/opbnb-docs/docs/tutorials/running-a-testnet-node#start-components. Use exactly the same commands once and see if it helps.
Also, seems like these following flags are missing too from your op-node
startup command:
Recommended for this: https://docs.bnbchain.org/opbnb-docs/docs/tutorials/running-a-testnet-node#start-components
Once this is all done, then pls share the output of curl commands as per this section: https://docs.bnbchain.org/opbnb-docs/docs/tutorials/running-a-testnet-node#check-status 1.
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://localhost:8545
2.
curl -X POST -H "Content-Type: application/json" --data \
'{"jsonrpc":"2.0","method":"optimism_syncStatus","params":[],"id":1}' \
http://localhost:8546 | jq .
Alright, everything's done. Sorry, at first, I didn't realize it was a request for the op-node
. Here are the responses to your queries.
{"jsonrpc":"2.0","id":1,"result":"0x8bc9d3"}
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"current_l1": {
"hash": "0xeb6b036323ce3da53df7d708165cf114f2921c437dc8d74fa0ffbf1f99ddc78a",
"number": 33781362,
"parentHash": "0x4d04c51bd90db977869d5bcbde1254812a2b5a06d83fc5cc7e2de2cfe3e28cd1",
"timestamp": 1696041127
},
"current_l1_finalized": {
"hash": "0x0d496fc1852e0e26d3d412434ebc44dc90ff70d5fe2fcd4b22b87fa7f953215a",
"number": 33795527,
"parentHash": "0x11776a07dacdf0f8ee3c6d76988a3959e230b8c32dbd0b5db8e5b0480d41392d",
"timestamp": 1696083622
},
"head_l1": {
"hash": "0xe250dce401883da727bca3d872ace1ac01d2565c93234ba434573d64b86267ca",
"number": 33795543,
"parentHash": "0xb95490bc31194f1b1fb6f03150e5bd4f8a3b8c6c5c6e2802467fe70266367160",
"timestamp": 1696083670
},
"safe_l1": {
"hash": "0xe250dce401883da727bca3d872ace1ac01d2565c93234ba434573d64b86267ca",
"number": 33795543,
"parentHash": "0xb95490bc31194f1b1fb6f03150e5bd4f8a3b8c6c5c6e2802467fe70266367160",
"timestamp": 1696083670
},
"finalized_l1": {
"hash": "0x0d496fc1852e0e26d3d412434ebc44dc90ff70d5fe2fcd4b22b87fa7f953215a",
"number": 33795527,
"parentHash": "0x11776a07dacdf0f8ee3c6d76988a3959e230b8c32dbd0b5db8e5b0480d41392d",
"timestamp": 1696083622
},
"unsafe_l2": {
"hash": "0x381e2315d2061c332e4031018d0302a641078a290e2dfd3916b7aacce2083861",
"number": 9161171,
"parentHash": "0x6b41eee7a8a5c5c8b6d09f68d3de4752abfac2b2265dd3f0ca5a2a711aa2129c",
"timestamp": 1696039677,
"l1origin": {
"hash": "0x26b7e00f86566780e2ec45b9eb5a7af6fc97213abcc61c4d7e9dc6210100d9dc",
"number": 33780878
},
"sequenceNumber": 2
},
"safe_l2": {
"hash": "0xffc0b74fa090821fd9be76a1ab62091b29fb97e6aeb8d3fefc3468633ccb0ff4",
"number": 9161012,
"parentHash": "0x3007689f385b785a2c21f08b10d55b7ba6c8c768a216c3df66e9fa5519aded74",
"timestamp": 1696039518,
"l1origin": {
"hash": "0xa913832c724f4cafc98bf404de8ce77d4002a39501471695d62299d6863c565e",
"number": 33780825
},
"sequenceNumber": 2
},
"finalized_l2": {
"hash": "0xffc0b74fa090821fd9be76a1ab62091b29fb97e6aeb8d3fefc3468633ccb0ff4",
"number": 9161012,
"parentHash": "0x3007689f385b785a2c21f08b10d55b7ba6c8c768a216c3df66e9fa5519aded74",
"timestamp": 1696039518,
"l1origin": {
"hash": "0xa913832c724f4cafc98bf404de8ce77d4002a39501471695d62299d6863c565e",
"number": 33780825
},
"sequenceNumber": 2
},
"queued_unsafe_l2": {
"hash": "0x58558e787c35bef179c9d5faa8fc754104da35d704856a303672d9b5f5abce80",
"number": 9204547,
"parentHash": "0xa8470b335b185dad5916cefa54e32ccb90f70724f4922b73bfe35f9d9fb6a629",
"timestamp": 1696083053,
"l1origin": {
"hash": "0x6ee8932c62dc6e6d024e76c1568843155e4d23cc9871acfeb742628aaf929881",
"number": 33795321
},
"sequenceNumber": 0
}
}
}
Could you put your op-geth and op-node configuration here? I did not see the L1 flags in your previous post.
Yes, of course. op-geth
"--datadir=/data",
"--verbosity=3",
"--http",
"--http.corsdomain=*",
"--http.vhosts=*",
"--http.addr=0.0.0.0",
"--http.port=8545",
"--http.api=net,eth,engine",
"--ws",
"--ws.addr=0.0.0.0",
"--ws.port=8545",
"--ws.origins=*",
"--ws.api=eth,engine",
"--syncmode=full",
"--maxpeers=10",
"--networkid=5611",
"--miner.gaslimit=150000000",
"--triesInMemory=32",
"--txpool.globalslots=10000",
"--txpool.globalqueue=5000",
"--txpool.accountqueue=200",
"--txpool.accountslots=200",
"--cache=32000",
"--cache.preimages",
"--allow-insecure-unlock",
"--authrpc.addr=0.0.0.0",
"--authrpc.port=8551",
"--authrpc.vhosts=*",
"--gcmode=archive",
"--metrics",
"--metrics.port=6060",
"--metrics.addr=0.0.0.0",
"--rollup.sequencerhttp=https://opbnb-testnet-rpc.bnbchain.org",
"--authrpc.jwtsecret=/local/jwtsecret"
op-node
"--l1.trustrpc",
"--sequencer.l1-confs=15",
"--verifier.l1-confs=15",
"--l1.http-poll-interval=3s",
"--l1.epoch-poll-interval=45s",
"--l1.rpc-max-batch-size=20",
"--rollup.config=/home/rollup.json",
"--rpc.addr=0.0.0.0",
"--rpc.port=8546",
"--p2p.sync.req-resp",
"--p2p.listen.ip=0.0.0.0",
"--p2p.listen.tcp=9003",
"--p2p.listen.udp=9003",
"--snapshotlog.file=./snapshot.log",
"--p2p.priv.raw=694dd51c94a31f1550bb2e3cb5535b4bce495488ddfcbafa79af77999fd5d6d3",
"--p2p.bootnodes=enr:-J24QGQBeMsXOaCCaLWtNFSfb2Gv50DjGOKToH2HUTAIn9yXImowlRoMDNuPNhSBZNQGCCE8eAl5O3dsONuuQp5Qix2GAYjB7KHSgmlkgnY0gmlwhDREiqaHb3BzdGFja4PrKwCJc2VjcDI1NmsxoQL4I9wpEVDcUb8bLWu6V8iPoN5w8E8q-GrS5WUCygYUQ4N0Y3CCIyuDdWRwgiMr",
"--metrics.enabled",
"--metrics.addr=0.0.0.0",
"--metrics.port=7300",
"--pprof.enabled",
"--rpc.enable-admin",
"--log.level=debug",
"--l1=https://data-seed-prebsc-1-s1.binance.org:8545",
"--l2=http://${NOMAD_UPSTREAM_ADDR_opbnb-ax52-host30-testnet-auth}",
"--l2.jwt-secret=/local/jwtsecret"
I have absolutely the same problem. Is there any solution here?
hm
@ynvv @blakelukas Sorry for the late reply.
There is a possibility that the node's chain has been forked and different with other nodes.
Would you please provide the following information, which will be very useful to locate the root cause:
The OP Node's rollup config. You can retrieve rollup config via RPC call optimism_rollupConfig
to OP Node, or the file rollup.config
directly.
Information about the blocks near the hard-fork height. There was a hard-fork happening at the height 5805494. Therefore, we can RPC call eth_getBlockByNumber(5805493)
, eth_getBlockByNumber(5805494)
and eth_getBlockByNumber(5805495)
to OP Geth to get the blocks info near the hard-fork height.
In the event that the chain is forked due to a hard fork, it is recommended to reset the blockchain and synchronize it with the latest version of the program:
Clear the data directory in OP Geth
Update the opbnb to latest version: git clone -b v0.2.1 git@github.com:bnb-chain/opbnb.git
Update the op-geth to latest version: git clone -b v0.2.0 git@github.com:bnb-chain/op-geth.git
Follow the instructions here to re-sync the testnet: https://docs.bnbchain.org/opbnb-docs/docs/tutorials/running-a-testnet-node . Just note that make sure to use the latest version of opbnb and op-geth, and use the new version genesis.json
and rollup.json
Please let me know if you have any questions or encounter any problems.
cc @ynvv @deepcrazy
Node cannot catch up with the current blocks testnet. It's consistently lagging behind by 40k blocks. We've tried using both a public node and our own node, and both are in sync. Here are the logs op-geth
op-node
Here's the configuration. op-geth
op-node
op-geth:v0.1.3
,op-node:v0.1.3
What could be the issue?