Nodes continue to fall behind

[COLUD4]

Hello! My locally deployed NEURO mainnet node continues to lag behind by about 21,700 blocks and cannot catch up. What can I do to restore the node?
Version:
us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101408.0
us-docker.pkg.dev/boba-392114/bobanetwork-tools-artifacts/images/op-node:v1.6.10

[breezytm]

I have a node experiencing the same issue.

Version:
us-docker.pkg.dev/boba-392114/bobanetwork-tools-artifacts/images/op-node:v1.6.8
us-docker.pkg.dev/boba-392114/bobanetwork-tools-artifacts/images/op-erigon:v1.2.0

[letsbangout]

I'm having the same issue, nodes stay persistently behind by about 12 hours. I'm running on op-geth (not sure the version, how do I check?) and i've now tried manually forcing op-node:v1.6.7 and 1.6.11. Neither of these resolve the issue which seems to be related to the op-node.

[boyuan-chen]

I'm having the same issue, nodes stay persistently behind by about 12 hours. I'm running on op-geth (not sure the version, how do I check?) and i've now tried manually forcing op-node:v1.6.7 and 1.6.11. Neither of these resolve the issue which seems to be related to the op-node.

Hey, could you please provide your configuration file?

[letsbangout]

I'm having the same issue, nodes stay persistently behind by about 12 hours. I'm running on op-geth (not sure the version, how do I check?) and i've now tried manually forcing op-node:v1.6.7 and 1.6.11. Neither of these resolve the issue which seems to be related to the op-node.

Hey, could you please provide your configuration file?

# cat docker-compose.yml
version: '3.4'

# The geth db can be downloaded from
# https://boba-db.s3.us-east-2.amazonaws.com/mainnet/boba-mainnet-geth-db-114909.tgz
# and extracted to the DATA_DIR

# The jwt-secret.txt file should be a random string of32 characters and should be kept secret.

# The p2p-node-key.txt is the private key used for the node to identify itself.

# The discovery and peerstore directories are used to store the peerstore and discovery data.

services:
  l2:
    image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101408.0
    command: >
      --datadir=/db
      --networkid=288
      --http
      --http.addr=0.0.0.0
      --http.port=9545
      --http.corsdomain=*
      --http.vhosts=*
      --authrpc.addr=0.0.0.0
      --authrpc.port=8551
      --authrpc.vhosts=*
      --authrpc.jwtsecret=/config/jwt-secret.txt
      --rollup.disabletxpoolgossip=true
      --http.api=eth,debug,net,web3
      --nodiscover
      --syncmode=full
      --maxpeers=0
      --rollup.sequencerhttp=https://mainnet.boba.network
    ports:
      - "9545:9545"
      - "8551:8551"
    volumes:
      - ./jwt-secret.txt:/config/jwt-secret.txt
      - /root/newgethdata:/db
  op-node:
    depends_on:
      - l2
    image: us-docker.pkg.dev/boba-392114/bobanetwork-tools-artifacts/images/op-node:v1.6.11
    command: >
      op-node
      --l1=${ETH1_HTTP:-https://mainnet.gateway.tenderly.co}
      --l1.beacon=${ETH2_HTTP}
      --l2=http://l2:8551
      --l2.jwt-secret=/config/jwt-secret.txt
      --network=boba-mainnet
      --rpc.addr=0.0.0.0
      --rpc.port=8545
      --p2p.ban.peers=false
      --p2p.priv.path=/config/p2p-node-key.txt
      --p2p.discovery.path=/p2p_discovery_db
      --p2p.peerstore.path=/p2p_peerstore_db
    ports:
      - "8545:8545"
    volumes:
      - ./jwt-secret.txt:/config/jwt-secret.txt
      - ./p2p-node-key.txt:/config/p2p-node-key.txt
      - ./discovery:/p2p_discovery_db
      - ./peerstore:/p2p_peerstore_db
    restart: always

[letsbangout]

I codified those specific versions based on the instructions here: https://docs.boba.network/developer/node-operators/software-release

[boyuan-chen]

Please check this branch #259

[boyuan-chen]

I think you missed the new hardforks

[letsbangout]

I think you missed the new hardforks

Ok but this started happening in September, long before the hardforks on the mainnet in October?

Also, I see that in the mainnet-geth .yml, it still references the old op-node 1.6.3:

"image: us-docker.pkg.dev/boba-392114/bobanetwork-tools-artifacts/images/op-node:v1.6.3"

Shouldn't this be 1.6.11 for the fork? Any other changes you should make before I try this?

Thanks.