Sepolia node is not able to find peers

[qedgardo]

My sepolia node (rpc) got stalled and it is not adding new blocks.
op-geth version: v1.101411.1
op-node version: v1.9.5

op-geth logs:

INFO [11-15|21:14:36.409] Ahead with major recommended protocol version change local=v8.0.0 required=v6.0.0-3 recommended=v6.0.0-3
INFO [11-15|21:14:44.535] Looking for peers                        peercount=1 tried=122 static=0

op-node logs:

op-node[2311671]: t=2024-11-15T21:18:17+0000 lvl=info msg="attempting connection" peer=16Uiu2HAkzLUbBeRLoGTouojEpXE3HMiJ7QJqfaVCzjXJDjrKpbLc
op-node[2311671]: t=2024-11-15T21:18:17+0000 lvl=info msg="attempting connection" peer=16Uiu2HAmPgFyxkixJ2PqVxaamSLukHdxG3pbmbtVSWjbsgHvnC2f

rollup.json:

{
  "genesis": {
    "l1": {
      "hash": "0x5fb818b4d3ba100eeb3347c508bca24752ee88f235120e108bd9ee5d1b2ae50b",
      "number": 6880819
    },
    "l2": {
      "hash": "0xe5fd5cf0be56af58ad5751b401410d6b7a09d830fa459789746a3d0dd1c79834",
      "number": 0
    },
    "l2_time": 1729003296,
    "system_config": {
      "scalar": "0x010000000000000000000000000000000000000000000000000c5fc500000558",
      "gasLimit": 30000000,
      "overhead": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "batcherAddr": "0x21e57c21530bc33f12ba96c9ddc135488365002f"
    }
  },
  "block_time": 1,
  "delta_time": 0,
  "fjord_time": 0,
  "canyon_time": 0,
  "l1_chain_id": 11155111,
  "l2_chain_id": 763373,
  "ecotone_time": 0,
  "granite_time": 0,
  "regolith_time": 0,
  "channel_timeout": 300,
  "seq_window_size": 3600,
  "batch_inbox_address": "0x004de1914f4f17ac234f5a5bc8a4072a231d44bf",
  "max_sequencer_drift": 600,
  "deposit_contract_address": "0x5c1d29c6c9c8b0800692acc95d700bcb4966a1d7",
  "l1_system_config_address": "0x05c993e60179f28bf649a2bb5b00b5f4283bd525",
  "protocol_versions_address": "0x79add5713b383daa0a138d3c4780c7a1804a8090"
}

[eitjuh]

@qedgardo
Thanks for reporting this issue!
Can you try to disable p2p on op-geth? Please let me know if it works and I'll update the docs!

[victorcheeney]

That's interesting, I'm also getting the same warnings, but on my end new blocks do get finalized. Can you run the following and see if your local finalized block matches the one on the RPC?

local_block=$(curl -s -X POST http://localhost:8545 -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["finalized", false],"id":1}' \
  | jq -r .result.number | sed 's/^0x//' | awk '{printf "%d\n", "0x" $0}'); \
remote_block=$(curl -s -X POST https://rpc-gel-sepolia.inkonchain.com/ -H "Content-Type: application/json" \
 --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["finalized", false],"id":1}' \
 | jq -r .result.number | sed 's/^0x//' | awk '{printf "%d\n", "0x" $0}'); \
echo -e "Local finalized block: $local_block\nRemote finalized block: $remote_block"

I'll try to figure out the source of the warnings in the meantime.

[qedgardo]

Hi @eitjuh , @ink-victor . Thanks for replying!
I disabled the p2p on op-geth (GETH_MAXPEERS="0" # Disables the network by setting the maximum number of peers to 0 GETH_NODISCOVER="true" # Disables the peer discovery mechanism) but the result was the same:

Nov 18 11:03:47 t-ink-sepolia-01 geth[2967019]: INFO [11-18|11:03:47.261] Ahead with major recommended protocol version change local=v8.0.0 required=v6.0.0-3 recommended=v6.0.0-3
Nov 18 11:03:47 t-ink-sepolia-01 geth[2967019]: INFO [11-18|11:03:47.261] Ahead with major required protocol version change local=v8.0.0 required=v6.0.0-3 recommended=v6.0.0-3
Nov 18 11:03:49 t-ink-sepolia-01 geth[2967019]: INFO [11-18|11:03:49.635] Looking for peers                        peercount=1 tried=0 static=0
Nov 18 11:03:59 t-ink-sepolia-01 geth[2967019]: INFO [11-18|11:03:59.741] Looking for peers                        peercount=1 tried=0 static=0
Nov 18 11:04:17 t-ink-sepolia-01 geth[2967019]: INFO [11-18|11:04:17.346] Looking for peers                        peercount=1 tried=0 static=0
Nov 18 11:04:30 t-ink-sepolia-01 geth[2967019]: INFO [11-18|11:04:30.549] Looking for peers                        peercount=1 tried=0 static=0

This is the curl output:

Local finalized block: 0
Remote finalized block: 0

From time to time, the node eventually got synced. And then starts showing the same warnings and got satlled

[victorcheeney]

Hey @qedgardo! Hope you're doing well. Sorry for the late replies. We're handling lots of different things at the same time in anticipation of the mainnet launch. 🙏

From time to time, the node eventually got synced. And then starts showing the same warnings and got satlled

That must be frustrating. I'll have to try resetting up my local node from a fresh snapshot and see if I can reproduce the error.

[victorcheeney]

Hey @qedgardo! Can you confirm that you have a .env file with valid L1 RPCs?

L1_RPC_URL=...
L1_BEACON_URL=...

https://github.com/inkonchain/node?tab=readme-ov-file#configuration-%EF%B8%8F

[qedgardo]

Hi @ink-victor ! thanks for replying.
I'm not running the node with docker-compose. I'm doing it with op-geth and op-node binaries.
I have the L1 endpoints where another L2 chains relies as well.

op-node args:

op-node \
    --syncmode=execution-layer \
    --l2.enginekind=geth \
    --l1.trustrpc \
    --l1.rpckind=basic \
    --l1=<http://eth-sepolia-rpc-endpoint> \
    --l1.beacon=<http://eth-sepolia-beacon-endpoint> \
    --l2=http://127.0.0.1:8551 \
    --rpc.addr=127.0.0.1 \
    --rpc.port=9545 \
    --l2.jwt-secret=/var/lib/ink/jwt.txt \
    --rollup.config=/var/lib/ink/config/rollup.json \
    --p2p.static=/ip4/34.32.241.134/tcp/9003/p2p/16Uiu2HAmKx8zPiN5WrbDW8hVRnwVXzfYdpt6PpPU6s98t5WtCTx5 \
    --p2p.bootnodes=enr:-Iu4QN7Ohk84lCZMSAbuPbU1vSMF93J7FUUab2_JBNX8q6wSPBeWrGu85ENsL-s2fcf9gvYc_Eiw8ZzdBzP5i05g9DwBgmlkgnY0gmlwhCP2ulGJc2VjcDI1NmsxoQLqBVn4RC7vvLvOB95odV2bp6zKCQHPw7j60wBG68qGJYN0Y3CCIyuDdWRwgiMs \
    --p2p.peerstore.path=/var/lib/ink/data/opnode_peerstore_db \
    --p2p.priv.path=/var/lib/ink/data/opnode_p2p_priv.txt \
    --p2p.discovery.path=/var/lib/ink/data/opnode_discovery_db \
    --sequencer.l1-confs=5 \
    --verifier.l1-confs=4 \
    --rollup.load-protocol-versions=true \
    --rollup.halt=major

op-geth args:

geth \
    --datadir=/var/lib/ink/data \
    --syncmode=snap \
    --gcmode=archive \
    --networkid="763373" \
    --http \
    --http.addr=0.0.0.0 \
    --http.port=8545 \
    --http.api=web3,debug,eth,net,engine,geth \
    --ws \
    --ws.port=8546 \
    --ws.addr=0.0.0.0 \
    --ws.api=debug,eth,net,engine \
    --authrpc.addr=127.0.0.1 \
    --authrpc.port=8551 \
    --authrpc.jwtsecret=/var/lib/ink/jwt.txt \
    --authrpc.vhosts="*" \
    --metrics \
    --metrics.addr=0.0.0.0 \
    --metrics.port=6060 \
    --port=30303 \
    --discovery.port=30303 \
    # This helps in the initial sync using snap sync
    --maxpeers=500 \
    --rollup.disabletxpoolgossip=true \
    --rollup.superchain-upgrades \
    --rollup.halt=major \
    --verbosity=3

[qedgardo]

Hi folks! do you have an update about this issue?

[victorcheeney]

Hey @qedgardo ! Not yet, sorry about this. Our setup is a standard OP node setup, I assume it should work fine if your flags match our environment variables in .env.sepolia.

[victorcheeney]

Hello @qedgardo! We've been able to reproduce the error and are actively working on this issue at this very moment.

[qedgardo]

Thanks for the update @ink-victor !

[Phantom722]

Thanks for the update @ink-victor !