Can't get my node working

Open rralcala opened this issue 11 months ago • 1 comments

Hey, I can't get my ink mainnet node to work, can you help me find what I might be doing wrong?

Here are my geth settings:

    --op-network=ink-mainnet \
    --datadir=/var/lib/ink/data \
    --syncmode=snap \
    --gcmode=archive \
    --http \
    --http.addr=0.0.0.0 \
    --http.port=8545 \
    --http.vhosts="*" \
    --http.corsdomain="*" \
    --http.api=web3,debug,eth,net,engine,geth \
    --ws \
    --ws.port=8546 \
    --ws.addr=0.0.0.0 \
    --ws.origins="*" \
    --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 \
    --maxpeers=500 \
    --rollup.sequencerhttp=https://rpc-gel.inkonchain.com \
    --rollup.disabletxpoolgossip=true \
    --rollup.superchain-upgrades \
    --rollup.halt=major \
    --override.holocene=1740582000 \
    --verbosity=3

And here are the node setting:

    --syncmode=execution-layer \
    --l2.enginekind=geth \
    --l1.trustrpc \
    --l1.rpckind=basic \
    --l1=http://[L1-ENDPOINT]:8545 \
    --l1.beacon=http://[L1-ENDPOINT]:5052 \
    --l2=http://127.0.0.1:8551 \
    --rpc.addr=127.0.0.1 \
    --rpc.port=9545 \
    --l2.jwt-secret=/var/lib/ink/jwt.txt \
    --network=ink-mainnet \
    --override.holocene=1740582000 \
    --p2p.static=/ip4/[IP]/tcp/9003/p2p/16Uiu2HAmECGb1vmBKhgxVHzX2aYkPcmV8CZjpPxrNkRiFA1wa3CN \
    --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 \
    --rollup.load-protocol-versions=true \
    --rollup.halt=major

op node logs:

Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="Starting JSON-RPC server"
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="Started JSON-RPC server" addr=127.0.0.1:9545
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="metrics disabled"
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="Starting execution engine driver"
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="Starting driver" sequencerEnabled=false sequencerStopped=false
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="Rollup node started"
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="State loop started"
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="connected to peer" peer=16Uiu2HAmECGb1vmBKhgxVHzX2aYkPcmV8CZjpPxrNkRiFA1wa3CN addr=/ip4/34.32.193.134/tcp/9003
Feb 28 16:30:37 m-ink-01 op-node[384090]: t=2025-02-28T16:30:37+0000 lvl=info msg="Starting P2P sync client event loop" peer=16Uiu2HAmECGb1vmBKhgxVHzX2aYkPcmV8CZjpPxrNkRiFA1wa3CN
Feb 28 16:30:47 m-ink-01 op-node[384090]: t=2025-02-28T16:30:47+0000 lvl=info msg="attempting connection" peer=16Uiu2HAmMJrhxpqbPTsjUUTTjJd2araJu2Z9nvsuGFeL8oxEvV97
Feb 28 16:30:47 m-ink-01 op-node[384090]: t=2025-02-28T16:30:47+0000 lvl=info msg="connected to peer" peer=16Uiu2HAmMJrhxpqbPTsjUUTTjJd2araJu2Z9nvsuGFeL8oxEvV97 addr=/ip4/217.22.153.180/tcp/30701
Feb 28 16:30:47 m-ink-01 op-node[384090]: t=2025-02-28T16:30:47+0000 lvl=info msg="Starting P2P sync client event loop" peer=16Uiu2HAmMJrhxpqbPTsjUUTTjJd2araJu2Z9nvsuGFeL8oxEvV97
Feb 28 16:30:48 m-ink-01 op-node[384090]: t=2025-02-28T16:30:48+0000 lvl=info msg="Received signed execution payload from p2p" id=0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837 peer=16Uiu2HAmMJrhxpqbPTsjUUTTjJd2araJu2Z9nvsuGFeL8oxEvV97 txs=1
Feb 28 16:30:48 m-ink-01 op-node[384090]: t=2025-02-28T16:30:48+0000 lvl=info msg="Optimistically inserting unsafe L2 execution payload to drive EL sync" id=0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837
Feb 28 16:30:48 m-ink-01 op-node[384090]: t=2025-02-28T16:30:48+0000 lvl=info msg="Starting EL sync"
Feb 28 16:30:48 m-ink-01 op-node[384090]: t=2025-02-28T16:30:48+0000 lvl=warn msg="Failed to insert unsafe payload for EL sync" id=0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837 err="temp: cannot process unsafe payload: new - 0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837; parent: 0xd22350469114f22cc48a4c0c57d23d3b5650d4f1e3c96b3d336903ddd727a511:7261836; err: execution payload 0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc0018ca100"
Feb 28 16:30:48 m-ink-01 op-node[384090]: t=2025-02-28T16:30:48+0000 lvl=warn msg="Payload was invalid" block=0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837 err="execution payload 0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc0018ca100" timestamp=1740760248
Feb 28 16:30:49 m-ink-01 op-node[384090]: t=2025-02-28T16:30:49+0000 lvl=info msg="Received signed execution payload from p2p" id=0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838 peer=16Uiu2HAmMJrhxpqbPTsjUUTTjJd2araJu2Z9nvsuGFeL8oxEvV97 txs=2
Feb 28 16:30:49 m-ink-01 op-node[384090]: t=2025-02-28T16:30:49+0000 lvl=info msg="Optimistically inserting unsafe L2 execution payload to drive EL sync" id=0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838
Feb 28 16:30:49 m-ink-01 op-node[384090]: t=2025-02-28T16:30:49+0000 lvl=warn msg="Failed to insert unsafe payload for EL sync" id=0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838 err="temp: cannot process unsafe payload: new - 0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838; parent: 0x1570517066361cb15f82f987a8edf8b928c69c542801a8566f02ebe072106c25:7261837; err: execution payload 0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc001916960"
Feb 28 16:30:49 m-ink-01 op-node[384090]: t=2025-02-28T16:30:49+0000 lvl=warn msg="Payload was invalid" block=0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838 err="execution payload 0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc001916960" timestamp=1740760249
Feb 28 16:30:49 m-ink-01 op-node[384090]: t=2025-02-28T16:30:49+0000 lvl=info msg="Received first L1 head signal" l1_head=0xd056668e5354f832cc005cf5a2ad968e71fdc6440c140e89f9ccb7cca71253d0:21946050
Feb 28 16:30:50 m-ink-01 op-node[384090]: t=2025-02-28T16:30:50+0000 lvl=info msg="Received signed execution payload from p2p" id=0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839 peer=16Uiu2HAmMJrhxpqbPTsjUUTTjJd2araJu2Z9nvsuGFeL8oxEvV97 txs=1
Feb 28 16:30:50 m-ink-01 op-node[384090]: t=2025-02-28T16:30:50+0000 lvl=info msg="Optimistically inserting unsafe L2 execution payload to drive EL sync" id=0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839
Feb 28 16:30:50 m-ink-01 op-node[384090]: t=2025-02-28T16:30:50+0000 lvl=warn msg="Failed to insert unsafe payload for EL sync" id=0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839 err="temp: cannot process unsafe payload: new - 0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839; parent: 0x3bbdafde61d99dd12f9fe63b42c75d59d85339465cfabd24378c157b975dc55b:7261838; err: execution payload 0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc0018cad80"
Feb 28 16:30:50 m-ink-01 op-node[384090]: t=2025-02-28T16:30:50+0000 lvl=warn msg="Payload was invalid" block=0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839 err="execution payload 0x4ea8cb337d70df959a0984297f264bb5e44691eacf27e73bda842a4f6b1a6915:7261839 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc0018cad80" timestamp=1740760250

op geth nodes:

Feb 28 15:42:02 m-ink-01 geth[375378]: INFO [02-28|15:42:02.075] Looking for peers                        peercount=2 tried=202 static=0

It seems to work when configuring the node in full archive mode

Sorry if some stuff is missing, I'm new here.

Feb 28 '25 16:02 rralcala

Hey @rralcala! Thanks for the issue. I contacted our RaaS and they told me that snap sync is not yet supported. I pushed a new release to the repo. Could you try it out and see how it goes?

Basically, you'd need to use --syncmode=full instead of --syncmode=snap for your geth settings.

Mar 04 '25 22:03 victorcheeney