Docker external-node frequently restart

[givenqiu]

🐛 Bug Report

Zksync docker external-node frequently restart after upgrading to v28.10.0-alpha-linux-amd64

📝 Description

Provide a clear and concise description of the bug.

Zksync Docker external-node frequently restart after upgrading to v28.10.0-alpha-linux-amd64

        "Name": "/zksync",
        "RestartCount": 9,

🔄 Reproduction Steps

Steps to reproduce the behaviour

🤔 Expected Behavior

Describe what you expected to happen.

😯 Current Behavior

Describe what actually happened.

🖥️ Environment

Any relevant environment details.

📋 Additional Context

Add any other context about the problem here. If applicable, add screenshots to help explain.

📎 Log Output

2025-08-11T06:06:10.367032Z DEBUG NamedFuture{name="transaction_finality_updater"}: zksync_health_check: Changed health of `transaction_finality_updater` from {"status":"ready","details":{"unfinalized_txs_checked":12}} to {"status":"shut_down"}
2025-08-11T06:06:10.367083Z ERROR zksync_node_framework::service: Task transaction_finality_updater failed: JSON-RPC request get_block_by_number(number=Safe, with_transactions=false) failed: client error (SendRequest)

Caused by:
    0: client error (SendRequest)
    1: http2 error
    2: connection error received: not a result of an error (b"max_age")
2025-08-11T06:06:10.367100Z  INFO zksync_node_framework::service: One of the task has exited, shutting down the node
2025-08-11T06:06:10.367159Z  INFO NamedFuture{name="postgres_metrics_scraping"}: zksync_dal::node::metrics: Stop request received, Postgres metrics scraping is shutting down
2025-08-11T06:06:10.367168Z  INFO zksync_node_api_server::healthcheck: Stop request received, healthcheck server is shutting down
Error: One or more tasks failed: ["Task transaction_finality_updater failed: JSON-RPC request get_block_by_number(number=Safe, with_transactions=false) failed: client error (SendRequest): client error (SendRequest): http2 error: connection error received: not a result of an error (b\"max_age\")"]

[cifer76]

+1, met this issue on v29.0.0 too.

this error seems happening every 1 hour

[givenqiu]

I have tried upgrade the node zksync-era to v29.1.1. But still have restart case with the following errors.

2025-08-25T00:22:25.112905Z  WARN NamedFuture{name="miniblock_precommit_fetcher"}: zksync_node_sync::miniblock_precommit_fetcher: Failed to fetch precommits from the main node: JSON-RPC request get_block_by_number(with_transactions=false, number=Safe) failed: ErrorObject { code: InternalError, message: "Internal error", data: None }
2025-08-25T00:22:25.158047Z DEBUG zksync_merkle_tree::pruning: No Merkle tree versions can be pruned; min stale key version is 501703, target retained version is 501702
2025-08-25T00:22:25.158069Z DEBUG zksync_merkle_tree::pruning: Pruning was not performed; waiting 60s
2025-08-25T00:22:25.628176Z DEBUG NamedFuture{name="data_availability_fetcher"}: zksync_node_sync::data_availability_fetcher: No L1 batches to fetch DA info for
2025-08-25T00:22:26.236460Z  WARN NamedFuture{name="transaction_finality_updater"}:observe_error{network="l2_9075" component=""}: zksync_web3_decl::client::metrics: Request `eth_getBlockByNumber` failed with HTTP error (response status: None): client error (SendRequest) method="eth_getBlockByNumber"
2025-08-25T00:22:26.236491Z  WARN NamedFuture{name="transaction_finality_updater"}: zksync_node_sync::transaction_finality_updater: Retryable error occurred while updating transactions: RPC error SL Node JSON-RPC request get_block_by_number(number=Safe, with_transactions=false) failed: client error (SendRequest). Retrying in 5
2025-08-25T00:22:27.630367Z DEBUG NamedFuture{name="data_availability_fetcher"}: zksync_node_sync::data_availability_fetcher: No L1 batches to fetch DA info for
2025-08-25T00:22:29.632994Z DEBUG NamedFuture{name="data_availability_fetcher"}: zksync_node_sync::data_availability_fetcher: No L1 batches to fetch DA info for
2025-08-25T00:22:31.237655Z  INFO NamedFuture{name="transaction_finality_updater"}: zksync_node_sync::transaction_finality_updater: Stop request received, exiting the batch transaction updater routine
2025-08-25T00:22:31.237736Z DEBUG NamedFuture{name="transaction_finality_updater"}: zksync_health_check: Changed health of `transaction_finality_updater` from {"status":"ready","details":{"unfinalized_txs_checked":14}} to {"status":"shut_down"}
2025-08-25T00:22:31.237866Z  INFO zksync_node_framework::service: Task transaction_finality_updater finished
2025-08-25T00:22:31.237881Z  INFO zksync_node_framework::service: One of the task has exited, shutting down the node
2025-08-25T00:22:31.237922Z DEBUG NamedFuture{name="web3_http_server"}: zksync_health_check: Changed health of `http_api` from {"status":"ready","details":{"local_addr":"0.0.0.0:3060"}} to {"status":"shutting_down"}
2025-08-25T00:22:31.237938Z  INFO NamedFuture{name="web3_http_server"}: zksync_node_api_server::web3: Stop request received, HTTP JSON-RPC server is shutting down