[Core Protocol] Problem after switching to Fusaka #892

neodiz · 2025-10-20T08:41:18Z

neodiz
Oct 20, 2025

Did you check the documentation and specs?

Yes

Was there anything unclear or missing?

No response

Did you check for duplicate questions?

Yes

Please select the type of request

Bug Report
Feature Request

Steps to Reproduce

No response

Expected vs. Actual Behaviour

No response

Software Versions

op-node 1.14.1
op-batcher 1.16.0

Operating System

OS Ubuntu 24.04
Docker version 27.5.1

Hardware Resources

No response

Configuration Files, Startup Flags & Environment Variables

    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.rpckind=erigon
      - --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

  geth:
    stop_grace_period: 300s
    command:
      - --http
      - --http.api=web3,debug,eth,txpool,net,engine,miner
      - --http.addr=0.0.0.0
      - --authrpc.vhosts=*
      - --http.vhosts=*
      - --http.corsdomain=*
      - --authrpc.addr=0.0.0.0
      - --authrpc.vhosts=*
      - --authrpc.port=8551
      - --ws
      - --ws.addr=0.0.0.0 
      - --ws.port=8546 
      - --ws.origins=* 
      - --ws.api=debug,eth,txpool,net,engine,miner
      - --authrpc.jwtsecret=/jwtsecret
      - --datadir=/data
      - --state.scheme=hash
      - --syncmode=full
      - --gcmode=archive
      - --networkid=${CHAIN_ID:-42093}
      - --nat=extip:$EXTERNAL_IP
      - --port=$GETH_P2P_PORT
      - --rollup.disabletxpoolgossip=true
      - --bootnodes=$BOOTNODE_GETH
      - --log.file=/logs/geth.log
      - --gpo.ignoreprice=1
      - --miner.gasprice=1
      - --txpool.pricelimit=1
      - --metrics
      - --metrics.port=9100
      - --metrics.addr=0.0.0.0 

  op-batcher:
     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=5
      - --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 


### Error Messages / Logs

op-node error
t=2025-10-20T08:36:47+0000 lvl=warn msg="Engine temporary error" err="derivation failed: temp: failed to fetch blobs: failed to get blob sidecars for L1BlockRef 0x3642fe29baa1d38311a772064488be58defe363928f92007713b7b0fa6f2b72d:9408958: failed to fetch blob sidecars for slot 8724918: failed request with status 500: {"code":500,"message":"INTERNAL_SERVER_ERROR: Insufficient data columns to reconstruct blobs: required 64, but only 4 were found.","stacktraces":[]}"
t=2025-10-20T08:36:47+0000 lvl=debug msg="scheduling re-attempt with delay" attempts=222 delay=10.085277861s
t=2025-10-20T08:36:47+0000 lvl=error msg="Engine failed temporarily, backing off sequencer" err="derivation failed: temp: failed to fetch blobs: failed to get blob sidecars for L1BlockRef 0x3642fe29baa1d38311a772064488be58defe363928f92007713b7b0fa6f2b72d:9408958: failed to fetch blob sidecars for slot 8724918: failed request with status 500: {"code":500,"message":"INTERNAL_SERVER_ERROR: Insufficient data columns to reconstruct blobs: required 64, but only 4 were found.","stacktraces":[]}"



### Feature Description

_No response_

### Purpose and Benefits

_No response_

### Relevant Context or Examples

_No response_

neodiz · 2025-10-20T08:52:23Z

neodiz
Oct 20, 2025
Author

and found warn message from op-batcher

t=2025-10-20T08:51:09+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939298 intensity=0.82872536385421 max_tx_size=3549 max_block_size=23923 controller_type=quadratic
t=2025-10-20T08:51:12+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939368 intensity=0.8287386397506944 max_tx_size=3549 max_block_size=23921 controller_type=quadratic
t=2025-10-20T08:51:14+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939438 intensity=0.8287519157535157 max_tx_size=3549 max_block_size=23919 controller_type=quadratic
t=2025-10-20T08:51:16+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939608 intensity=0.8287841579173612 max_tx_size=3548 max_block_size=23915 controller_type=quadratic
t=2025-10-20T08:51:18+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939678 intensity=0.8287974342847656 max_tx_size=3548 max_block_size=23913 controller_type=quadratic
t=2025-10-20T08:51:19+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939748 intensity=0.8288107107585069 max_tx_size=3548 max_block_size=23912 controller_type=quadratic
t=2025-10-20T08:51:22+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939294 intensity=0.8287246052347657 max_tx_size=3549 max_block_size=23923 controller_type=quadratic
t=2025-10-20T08:51:24+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939364 intensity=0.8287378811251737 max_tx_size=3549 max_block_size=23921 controller_type=quadratic
t=2025-10-20T08:51:26+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11939434 intensity=0.8287511571219184 max_tx_size=3549 max_block_size=23919 controller_type=quadratic
t=2025-10-20T08:51:28+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11941505 intensity=0.8291439850805663 max_tx_size=3541 max_block_size=23869 controller_type=quadratic
t=2025-10-20T08:51:29+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11941575 intensity=0.8291572643296984 max_tx_size=3541 max_block_size=23867 controller_type=quadratic
t=2025-10-20T08:51:32+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11941645 intensity=0.8291705436851671 max_tx_size=3540 max_block_size=23866 controller_type=quadratic
t=2025-10-20T08:51:34+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11941715 intensity=0.8291838231469727 max_tx_size=3540 max_block_size=23864 controller_type=quadratic
t=2025-10-20T08:51:36+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11941885 intensity=0.8292160737112086 max_tx_size=3540 max_block_size=23860 controller_type=quadratic
t=2025-10-20T08:51:38+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11941955 intensity=0.8292293535375976 max_tx_size=3539 max_block_size=23858 controller_type=quadratic
t=2025-10-20T08:51:40+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11942025 intensity=0.8292426334703233 max_tx_size=3539 max_block_size=23856 controller_type=quadratic
t=2025-10-20T08:51:42+0000 lvl=warn msg="Throttling loop: unsafe bytes above threshold, scaling endpoint throttling based on intensity" unsafe_bytes=11942195 intensity=0.8292748851782227 max_tx_size=3538 max_block_size=23852 controller_type=quadratic

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[Core Protocol] Problem after switching to Fusaka #892

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

[Core Protocol] Problem after switching to Fusaka #892

Uh oh!

neodiz Oct 20, 2025

Did you check the documentation and specs?

Was there anything unclear or missing?

Did you check for duplicate questions?

Similar Questions or Issues Found

Please select the type of request

Steps to Reproduce

Expected vs. Actual Behaviour

Software Versions

Operating System

Hardware Resources

Configuration Files, Startup Flags & Environment Variables

Replies: 1 comment

Uh oh!

Uh oh!

neodiz Oct 20, 2025 Author

neodiz
Oct 20, 2025

neodiz
Oct 20, 2025
Author