op-node errors with: 'failed to setup: unable to create the rollup node: failed to init L2: incorrect L2 RPC chain id 1, expected 10'

[lootboi]

OP-Mainnet Archive node setup errors

When attempting to sync an op-mainnet archive node from bedrock data and an archival snapshot, the ./run-op-geth.sh command errors with:

message="failed to setup: unable to create the rollup node: failed to init L2: incorrect L2 RPC chain id 1, expected 10".

This is apart of the Building a Node from Source guide at this step.

Scripts:

run-l2geth.sh:

cd /data/optimism-legacy/l2geth

USING_OVM=true \
  ETH1_SYNC_SERVICE_ENABLE=false \
  RPC_API=eth,rollup,uet,web3,debug \
  RPC_ENABLE=true \
  RPC_PORT=8888 \
  ./build/bin/geth --datadir ./datadir

run-op-geth.sh

#! /usr/bin/bash

SEQUENCER_URL=https://mainnet-sequencer.optimism.io/

cd /data/op-geth

./build/bin/geth \
  --port 30304 \
  --datadir=./datadir \
  --http \
  --http.port=8545 \
  --http.addr=0.0.0.0 \
  --authrpc.addr=localhost \
  --authrpc.jwtsecret=./jwt.txt \
  --verbosity=3 \
  --rollup.sequencerhttp=$SEQUENCER_URL \
  --nodiscover \
  --syncmode=full \
  --maxpeers=0 \
  --rollup.historicalrpc=http://localhost:8888 \
  --gcmode=archive \

run-op-node.sh (erroring script)

#!/usr/bin/bash

L1URL=https://<hidden>.quiknode.pro/<>hidden/
L1KIND=quicknode
NET=mainnet

cd /data/optimism/op-node/


./bin/op-node \
    --l1=$L1URL  \
    --l1.rpckind=$L1KIND \
    --l2=ws://localhost:8551 \
    --l2.jwt-secret=./jwt.txt \
    --network=$NET \
    --rpc.addr=0.0.0.0 \
    --rpc.port=8547

This is the rollup config:

INFO [11-17|00:16:04.718] Rollup Config                            l2_chain_id=10 l2_network=OP-Mainnet l1_chain_id=1 l1_network=mainnet l2_start_time=1,686,068,903 l2_block_hash=0xdbf6a80fef073de06add9b0d14026d6e5a86c85f6d102c36d3d8e9cf89c2afd3 l2_block_number=105,235,063 l1_block_hash=0x438335a20d98863a4c0c97999eb2481921ccd28553eac6f913af7c12aec04108 l1_block_number=17,422,590 regolith_time="@ genesis" canyon_time="(not configured)" span_batch_time="(not configured)"

[sbvegan]

I see the issue and I'll work on fixing this in the docs! We're actually in the process of migrating our documentation website to: https://docs.optimism.io/

The data directory path in the op-geth and l2geth script might be wrong. However these are two different data directories, so you'll need to specify two different paths.

I'll make those updates here: https://docs.optimism.io/node-operators/building-node/mainnet

[sbvegan]

I simplified the tutorial by:

• removing the scripts aspect and just executing the commands directly
• sharing the jwt.txt file across the op-geth and op-node
• clarified the data directory paths

ethereum-optimism/docs#175

[sbvegan]

Getting back to the originally reported issue. Let's take a look at the log message.

message="failed to setup: unable to create the rollup node: failed to init L2: incorrect L2 RPC chain id 1, expected 10"

This means that the --l2 parameter was pointing to a L1 node. The chain id of Ethereum is 1 and OP Mainnet is 10. So we take a look at that parameter.

--l2=ws://localhost:8551

The script looks right, this is default location for the authrpc host and port. So its pointed at op-geth, but there's something up. This must mean that op-geth started, but was not properly configured as a L2 node. If its started up without a L2 configuration, op-geth gets confused and just starts running as a L1 ethereum node. Thats why we're seeing a reported chain id as 1. Rollup nodes can either be configured with either a genesis file or a data directory.

1. With a Genesis File: This is for OP Sepolia, and other testnets or deployments that are not migrated from a legacy network. In this case, you'll download the genesis file and initialize the data directory via geth init.
2. With a Data Directory: This is used for networks that are migrated from a legacy network. This would include OP Mainnet and OP Goerli. In this case, you'll download a preconfigured data directory and extract it. No further initialization is necessary in this case, because the data directory contains the network's genesis information.

Our OP Mainnet nodes are configured with a data directory. So this leads me to believe that your op-geth execution script is pointing to the wrong --datadir path.

[github-actions[bot]]

Hey @lootboi, 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.