Skip to content

Problems after migrating to the Fusaka network. Errors in the op-node #893

@neodiz

Description

@neodiz

Bug Description
I have a network connected to Sepolia. Transactions are stuck in pending mode. Restarting op-batcher temporarily solves the problem. I also see an error in the op-node logs. Op-batcher also has a warning message

Steps to Reproduce
The problem started after updating Kusaka
Expected behavior

Environment Information:

  • Ubuntu 22.04
  • docker version 27.5.1
  • op-geth Geth/v1.101603.1-stable-8da5bf08/linux-amd64/go1.24.
  • op-node version v0.0.0-c1081e3a-1759886077(14.1) build from source
  • op-batcher version v1.16.0-64cb0d24-1758896861

Configurations:

    image: "repo.mind-dev.com/sanchain/op-node:v1.14.1"
    command: 
      - op-node
      - --l2=http://geth:8551 
      - --l2.jwt-secret=/jwtsecret
      - --sequencer.enabled 
      - --l1.trustrpc=true
      - --sequencer.l1-confs=5 
      - --verifier.l1-confs=4 
      - --rollup.config=/files/rollup.json 
      - --rpc.addr=0.0.0.0
      - --rpc.enable-admin 
      - --p2p.sequencer.key=$SEQUENSER_KEY
      - --l1=$L1_NODE
      - --l1.beacon=$L1_BEACON
      - --log.level=Debug
      - --p2p.listen.tcp=9222
      - --p2p.listen.udp=9222
      - --p2p.advertise.ip=$EXTERNAL_IP
      - --p2p.bootnodes=$BOOTNODE_NODE
      - --safedb.path=/db
      - --metrics.enabled
      - --metrics.port=9100
      - --metrics.addr=0.0.0.0
      
  op-batcher
    image: "us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:64cb0d2490fea1b00dcce80aa2f39bafc47a2010"
    command:
      - op-batcher
      - --l2-eth-rpc=http://geth:8545 
      - --rollup-rpc=http://op-node:9545 
      - --poll-interval=1s 
      - --sub-safety-margin=6 
      - --num-confirmations=1 
      - --safe-abort-nonce-too-low-count=3 
      - --resubmission-timeout=30s 
      - --rpc.addr=0.0.0.0 
      - --rpc.port=8548 
      - --rpc.enable-admin 
      - --max-channel-duration=150
      - --target-num-frames=5
      - --txmgr.min-basefee=2
      - --txmgr.min-tip-cap=2
      - --batch-type=1
      - --compression-algo=brotli-11 
      - --data-availability-type=blobs 
      - --approx-compr-ratio=0.9 
      - --max-l1-tx-size-bytes=240000 
      - --l1-eth-rpc=$L1_NODE 
      - --private-key=$BATCHER_KEY
      - --log.level=debug
      - --metrics.enabled
      - --metrics.port=9100
      - --metrics.addr=0.0.0.0

Logs:

op-node 
t=2025-10-23T07:55:09+0000 lvl=warn msg="Engine temporary error" err="derivation failed: temp: failed to fetch blobs: expected 2 blobs but got 8"
t=2025-10-23T07:55:09+0000 lvl=debug msg="scheduling re-attempt with delay" attempts=4997 delay=10.21348529s
t=2025-10-23T07:55:09+0000 lvl=error msg="Engine failed temporarily, backing off sequencer" err="derivation failed: temp: failed to fetch blobs: expected 2 blobs but got 8"
t=2025-10-23T07:55:09+0000 lvl=debug msg="Sequencer action schedule changed" t=2025-10-23T07:55:10+0000 wait=999.99987ms ok=true event=engine-temporary-error

Additional context
The problem started after updating Kusaka

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions