search

bnb-chain / opbnb-node-docker

36 stars 25 forks source link

I can't using my private L1 BSC rpc for opbnb #8

Closed kugimiya530 closed 2 weeks ago

kugimiya530 commented 9 months ago

using public L1 node is ok

but if i using my private bsc rpc will error , output is below

My private RPC at bsc was work

t=2023-12-19T23:51:17+0000 lvl=info msg="Initializing Rollup Node" t=2023-12-19T23:51:17+0000 lvl=warn msg="Unknown env var" prefix=OP_NODE env_var="OP_NODE_IMAGE_TAG=latest" t=2023-12-19T23:51:17+0000 lvl=warn msg="Unknown env var" prefix=OP_NODE env_var="OP_NODE__RPC_ENDPOINT=my private BSC rpc" t=2023-12-19T23:51:17+0000 lvl=info msg="Key manager " keyType=OP_NODE_P2P_SEQUENCER_KEY t=2023-12-19T23:51:17+0000 lvl=info msg="Key manager is skipped" t=2023-12-19T23:51:17+0000 lvl=info msg="Rollup Config" l2_chain_id=204 l2_network=opBNBMainnet l1_chain_id=56 l1_network="unknown L1" l2_start_time=1,691,753,723 l2_block_hash=0x4dd61178c8b0f01670c231597e7bcb368e84545acd46d940a896d6a791dd6df4 l2_block_number=0 l1_block_hash=0x29443b21507894febe7700f7c5cd3569cc8bf1ba535df0489276d8004af81044 l1_block_number=30,758,357 regolith_time="@ genesis" Fermat=9,397,477 t=2023-12-19T23:51:17+0000 lvl=eror msg="Error initializing the rollup node" err="failed to fetch header by num 30758357: not found" t=2023-12-19T23:51:17+0000 lvl=eror msg="Unable to create the rollup node" error="failed to fetch header by num 30758357: not found" t=2023-12-19T23:51:17+0000 lvl=crit msg="Application failed" message="failed to fetch header by num 30758357: not found"

STdevK commented 9 months ago

What is your node startup command? Can you share more information about the config?

kugimiya530 commented 9 months ago

What is your node startup command? Can you share more information about the config?

did u mean BSC or OPBNB

if opbnb i was using docker , and just modify .env

STdevK commented 7 months ago

Yes for your private BSC RPC. Did you try swapping with a BSC service provider RPC to check if it works?

neoromantique commented 7 months ago

Can confirm, same error.

We launch our L1 as follows, config being mostly default:

./geth_linux_1.3.7 --config ./config.toml --datadir ./node --snapshot=true --cache 18000 --rpc.allow-unprotected-txs --txlookuplimit 0 --metrics...
HTTPModules = ["eth", "net", "web3", "txpool", "parlia"]
STdevK commented 7 months ago

Please check if your L1 node is synced correctly, there're some changes to the startup command flags.

--txlookuplimit was abandoned officially since v1.3.3, replaced by flag: --history.transactions

Follow the flags when usng pebbleDB https://forum.bnbchain.org/t/faq-pbss-pebbledb/2260

ymonye commented 4 months ago

I'm getting this same exact error as the OP. Using a public RPC works fine, but then Node-Real BSC-Erigon v1.2.8 has issues.

t=2024-05-21T03:05:54+0000 lvl=crit msg="Application failed" message="failed to setup: unable to create the rollup node: failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 30758357: not found"

Curling eth_blockNumber to my Node-Real BSC node works without issue. The result also lines up with BSC's latest block at the moment:

curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' <my-bsc-node-ip-port>

{"jsonrpc":"2.0","id":1,"result":"0x251a45a"}

welkin22 commented 1 month ago

I'm getting this same exact error as the OP. Using a public RPC works fine, but then Node-Real BSC-Erigon v1.2.8 has issues.

t=2024-05-21T03:05:54+0000 lvl=crit msg="Application failed" message="failed to setup: unable to create the rollup node: failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 30758357: not found"

Curling eth_blockNumber to my Node-Real BSC node works without issue. The result also lines up with BSC's latest block at the moment:

curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' <my-bsc-node-ip-port>

{"jsonrpc":"2.0","id":1,"result":"0x251a45a"}

@ymonye hi, adding a line --log.level=debug to the startup command in the scripts/op-node-start.sh file can enable debug logging, then please upload the complete log so that we can troubleshoot the issue.

welkin22 commented 2 weeks ago

Since there has been no activity for a long time, I will close this issue for now. Please feel free to reopen it if necessary.