Closed AntonieDavid closed 1 month ago
joshieDo
commented
2 months ago There is an extra flag which is mentioned on running optimism, but went amiss on the specific op-mainnet page: https://github.com/paradigmxyz/reth/pull/10289
--l2.enginekind=reth should also be added to the running command.
At the same time, can you double check your import ? it shows the latest block as 0, but it should be higher
AntonieDavid
commented
2 months ago I made a mistake regarding the logs provided (i copied logs from the wrong node which as you mentioned had incomplete import of blocks), the correct op-reth logs looked similar to this, except they were at 100% for a long time before restarting the service (can't regenerate those logs as I restarted the service).
Aug 07 01:34:07 optimism-archive-mainnet-0-euc1 op-reth[1020504]: 2024-08-07T01:34:07.021001Z INFO Status connected_peers=15 freelist=3098403 stage=Bodies checkpoint=108992000 target=123681893 stage_progress=88.12%
Regarding the mentioned flag for op-node, I couldn't find the reference to it in op-node --help and also it returns an undefined flag error:
t=2024-08-14T00:20:16+0000 lvl=crit msg="Application failed" message="flag provided but not defined: -l2.enginekind"
github-actions[bot]
commented
1 month ago This issue is stale because it has been open for 21 days with no activity.
github-actions[bot]
commented
1 month ago This issue was closed because it has been inactive for 7 days since being marked as stale.
Describe the bug
I have followed the documentation regarding exporting/importing the prebedrock chain and right after starting the op-reth and op-node services, the op-node logs show the same error detailed in the node logs below. It's been 2 days since startup and nothing has changed. Op-reth logs looked all right at the begining, but for some time now (more than 1/2 a day) it has been stuck showing the logs presented below. Probably a restart would solve the op-reth issue, but I think it's related to op-node and it will get stuck again eventually. I am attaching the service files used to run the nodes. Worth mentioning that I am running 2 nodes with the only difference being that one has
--debug.tip 0xef96c413427e0b350953039ca23c49a28f80cd22c87a61c0b25ae27da1ae769din the op-reth configs and the other doesn't, but still showing the exact same error on both.ExecStart=/usr/local/bin/op-reth node \ --ws --ws.port=8546 --ws.addr=0.0.0.0 --ws.origins="*" \ --http --http.port=8545 --http.addr=0.0.0.0 \ --http.corsdomain="*" \ --authrpc.addr=0.0.0.0 \ --authrpc.jwtsecret=/node/data/secret.jwt \ --authrpc.port=8551 \ --datadir=/node/data/reth/ \ --rollup.sequencer-http=https://mainnet-sequencer.optimism.io/ \ --http.api=admin,debug,eth,net,trace,web3,rpc,reth,ots,eth-call-bundle \ --ws.api=admin,debug,eth,net,trace,web3,rpc,reth,ots,eth-call-bundle \ --metrics 0.0.0.0:6060 \ --chain optimism \ --rpc.gascap 18446744073709551615 \ --rpc.max-connections 429496729 \ --rpc.max-logs-per-response 0 \ --rpc.max-subscriptions-per-connection 10000 \ --rollup.disable-tx-pool-gossip \ --debug.tip 0xef96c413427e0b350953039ca23c49a28f80cd22c87a61c0b25ae27da1ae769dExecStart=/usr/local/bin/op-node --l1.trustrpc=true --l1=https://eth-mainnet.... \ --l2=ws://localhost:8551 --rpc.addr=0.0.0.0 \ --rpc.port=9545 --l2.jwt-secret=/node/data/secret.jwt \ --metrics.enabled --network op-mainnet --l1.beacon http://...... \ --syncmode=execution-layerSteps to reproduce
Starting the node with the mentioned conditions. Main issue is in op-node logs.
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
op-reth --version reth Version: 1.0.4 Commit SHA: e24e4c773d7571a5a54dba7854643c02d0b0a841 Build Timestamp: 2024-08-07T14:53:14.988149886Z Build Features: asm_keccak,jemalloc,optimism Build Profile: maxperf
What database version are you on?
op-reth db version 2024-08-13T07:04:51.376236Z INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/optimism Current database version: 2 Local database version: 2
Which chain / network are you on?
optimism mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
[stages.prune] commit_threshold = 1000000
If you've built Reth from source, provide the full command you used
source "$HOME/.cargo/env" && RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf --features jemalloc,asm-keccak,optimism --bin op-reth
Code of Conduct