search

base-org / node

Everything required to run your own Base node
https://base.org
MIT License
68.22k stars 2.55k forks source link

Cannot configure network and rollup-config at the same time #259

Closed tinchomengo closed 5 months ago

tinchomengo commented 5 months ago

Hey everyone! I'm getting the following error logs while trying to run the Base Node on Mainnet, which ends up on the 'basenode-node-1' container exiting, while the 'basenode-geth-1' container keeps running with no problem. Help on this will be enormously appreciated!

2024-05-19 02:25:55 waiting for geth to be ready

2024-05-19 02:26:10 fetched public IP is: 169.155.244.245

2024-05-19 02:26:15 t=2024-05-19T01:26:15+0000 lvl=warn msg="Unknown env var" prefix=OP_NODE env_var="OP_NODE_L2_ENGINE_AUTH_RAW=688f5d737bad920bdfb2fc2f488d6b6209eebda1dae949a8de91398d932c517a"

2024-05-19 02:26:15 t=2024-05-19T01:26:15+0000 lvl=warn msg="Found a deprecated flag which will be removed in a future version" flag_name=beta.extra-networks

2024-05-19 02:26:15 t=2024-05-19T01:26:15+0000 lvl=warn msg="The beta.extra-networks flag is deprecated and can be omitted safely."

2024-05-19 02:26:15 t=2024-05-19T01:26:15+0000 lvl=eror msg="Cannot configure network and rollup-config at the same time.\nStartup will proceed to use the network-parameter and ignore the rollup config.\nConflicting configuration is deprecated, and will stop the op-node from starting in the future.\n" network=base-mainnet rollup_config=mainnet/rollup.json

2024-05-19 02:26:15 t=2024-05-19T01:26:15+0000 lvl=info msg="Rollup Config" l2_chain_id=8453 l2_network=Base l1_chain_id=1 l1_network=mainnet l2_start_time=1686789347 l2_block_hash=0xf712aa9241cc24369b143cf6dce85f0902a9731e70d66818a3a5845b296c73dd l2_block_number=0 l1_block_hash=0x5c13d307623a926cd31415036c8b7fa14572f9dac64528e857a470511fc30771 l1_block_number=17481768 regolith_time="@ genesis" canyon_time="@ 1704992401 ~ Thu Jan 11 17:00:01 UTC 2024" delta_time="@ 1708560000 ~ Thu Feb 22 00:00:00 UTC 2024" ecotone_time="@ 1710374401 ~ Thu Mar 14 00:00:01 UTC 2024" fjord_time="(not configured)" interop_time="(not configured)"

2024-05-19 02:26:15 t=2024-05-19T01:26:15+0000 lvl=info msg="Initializing rollup node" version=v1.7.1-c87a469d-1709078315

2024-05-19 02:26:16 t=2024-05-19T01:26:16+0000 lvl=eror msg="Error initializing the rollup node" err="failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 17481768: not found"

2024-05-19 02:26:16 t=2024-05-19T01:26:16+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 17481768: not found"

Context: I'm running my own Ethereum L1, and therefore my OP_NODE_L1_ETH_RPC and OP_NODE_L1_BEACON in my .env.mainnet file are set to the IP addresses that this Ethereum L1 gives me, which are correct, as I have other different nodes using this RPC and Beacon URLs. I followed the guide shown on the Base Node website, where the .env.mainnet file had to be updated with the 2 variables mentioned above (done), and I needed to run a 'docker compose up --build'. Also I removed the 'geth-data' folder before running the 'docker compose up --build', as I was having some trouble where the 'basenode-node-1' was properly running, while the 'basenode-geth-1' container was not, but now it's the opposite situation.

For reference these are the logs I'm getting on the 'basenode-geth-1' container:

(...)
2024-05-19 03:05:02 INFO [05-19|02:05:02.397] Looking for peers                        peercount=2 tried=163 static=0
2024-05-19 03:05:12 INFO [05-19|02:05:12.551] Looking for peers                        peercount=2 tried=90  static=0
2024-05-19 03:05:22 INFO [05-19|02:05:22.621] Looking for peers                        peercount=2 tried=53  static=0
2024-05-19 03:05:32 INFO [05-19|02:05:32.630] Looking for peers                        peercount=2 tried=162 static=0
2024-05-19 03:05:42 INFO [05-19|02:05:42.630] Looking for peers                        peercount=2 tried=133 static=0
2024-05-19 03:06:03 INFO [05-19|02:06:03.286] Looking for peers                        peercount=2 tried=109 static=0
2024-05-19 03:06:13 INFO [05-19|02:06:13.304] Looking for peers                        peercount=2 tried=105 static=0
2024-05-19 03:06:23 INFO [05-19|02:06:23.309] Looking for peers                        peercount=2 tried=107 static=0
(...)
wbnns commented 5 months ago

@tinchomengo Hi there! Are you running your node in snap sync by chance (see the bottom of the env); if not, please make sure you can reach your endpoints from within the docker container.

Sounds like one of these two issues are most likely the culprit. Please let me know if not and will reopen! :)