Fresh rpc node dont start.

[Nich01asFox]

Describe the bug

Hi all.
I try to start fresh rpc node, but no luck. i try two times to reinstall node and redownload snapshot, but no luck. How fix this ?

Steps to reproduce

1. Install latest Docker engine and compose on Ubuntu 24.04
2. run container that download latest snapshot
   docker run -d -v tempo_cache:/root/.cache/reth -v tempo_local:/root/.local/share/reth --name tempo-snap ghcr.io/tempoxyz/tempo:latest download
3. After snapshot download and unpak , run this compose file

version: '3.8'

services:
 tempo-node:
   image: ghcr.io/tempoxyz/tempo:${IMG_TAG:-latest}
   container_name: tempo-node
   restart: always
   command: node --follow --port 30303 --discovery.addr 0.0.0.0 --discovery.port 30303 --http --http.addr 0.0.0.0 --http.port 8545 --http.api eth,net,web3,txpool,trace --metrics 9000
   ports:
     - "30303:30303"   # P2P
     - "8545:8545"     # HTTP JSON-RPC
   volumes:
     - tempo_cache:/root/.cache/reth
     - tempo_local:/root/.local/share/reth
volumes:
   tempo_cache:
       external: true
   tempo_local:
       external: true

Logs

~# docker logs --tail 20 tempo-node 
Error: execution node failed

Caused by:
   0: failed launching execution node
   1: genesis hash in the storage does not match the specified chainspec: chainspec is 0x49d7ec7085e77bf5a403d0fcb4cfc42a4084a89dfff60477579c5e09c9e03c54, database is 0xba49153e6f3996a340f3fe3d69e7c0826b717ae672cb115cf0527cada0b78e9e
2026-02-06T14:18:04.847552Z  INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/tempo
2026-02-06T14:18:04.849097Z  INFO Starting Tempo version="1.1.0 (010654b)"
2026-02-06T14:18:04.849154Z  INFO Opening database path="/root/.local/share/reth/tempo/db"
2026-02-06T14:18:04.906217Z  INFO Configuration loaded path="/root/.local/share/reth/tempo/reth.toml"
2026-02-06T14:18:04.906919Z  INFO Healing static file inconsistencies.
2026-02-06T14:18:05.036899Z  INFO Verifying storage consistency.
2026-02-06T14:18:05.037081Z  INFO Database opened
2026-02-06T14:18:05.037110Z  INFO Storage settings settings=Some(StorageSettings { receipts_in_static_files: false, transaction_senders_in_static_files: false, storages_history_in_rocksdb: false, transaction_hash_numbers_in_rocksdb: false, account_history_in_rocksdb: false, account_changesets_in_static_files: false })
2026-02-06T14:18:05.037189Z  INFO Starting metrics endpoint at 127.0.0.1:9000
2026-02-06T14:18:05.037484Z ERROR shutting down due to error
Error: execution node failed

Caused by:
   0: failed launching execution node
   1: genesis hash in the storage does not match the specified chainspec: chainspec is 0x49d7ec7085e77bf5a403d0fcb4cfc42a4084a89dfff60477579c5e09c9e03c54, database is 0xba49153e6f3996a340f3fe3d69e7c0826b717ae672cb115cf0527cada0b78e9e

Platform(s)

Linux (x86)

Container Type

Docker

What version/commit are you on?

latest docker image from your repo ghcr.io/tempoxyz/tempo:latest

If you've built from source, provide the full command you used

No response

Code of Conduct

• I agree to follow the Code of Conduct

[ahmedbolanta]

Hi @Nich01asFox,

I've been running a Tempo node for about 2 months and encountered the same issue. The error you're seeing is a chainspec mismatch, the genesis hash stored in your database doesn't match what the current version expects.

The fastest fix is to clear the database and let it resync with the current chainspec:

docker volume rm tempo_local
docker-compose up -d

This removes only the database (the tempo_local volume), keeping your cached snapshot (tempo_cache), so the resync is much faster than starting completely fresh.

To Prevent Future Issues

Also, consider pinning a specific stable version instead of using latest. Update your docker-compose file:

services:
  tempo-node:
    image: ghcr.io/tempoxyz/tempo:v1.0.0  # Use a specific version instead of latest

Using latest can pull breaking changes when the image is updated. Pinning a version gives you control over when to upgrade.

give it a try and let me know if you hit any issues!

[Nich01asFox]

Hi @ahmedbolanta

I attempted to fix the node using the steps you provided and received a new error.
I will describe my steps in sequence.

1. i Delete all containers and volumes.
2. Download fresh snapshot by running
   docker run -d -v tempo_cache:/root/.cache/reth -v tempo_local:/root/.local/share/reth --name tempo-snap ghcr.io/tempoxyz/tempo:1.1.0 download
3. Fix my compose with image version 1.1.0 and run node container by docker compose up -d and i get the same error that i reported.
4. Next i stop and remove node container tempo-node and remove tempo_local volume as you say.
5. Create new empty volume docker volume create tempo_local and run compose
6. i get new error in logs

thread 'tokio-runtime-worker' (16) panicked at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-util-0.3.31/src/stream/stream/select_next_some.rs:32:9:
SelectNextSome polled after terminated
stack backtrace:
   0: __rustc::rust_begin_unwind
             at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/std/src/panicking.rs:698:5
   1: core::panicking::panic_fmt
             at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/core/src/panicking.rs:75:14
   2: core::panicking::panic
2026-02-09T11:32:45.477399Z  INFO RPC HTTP server started url=0.0.0.0:8545
2026-02-09T11:32:45.477594Z  INFO Starting consensus engine
             at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/core/src/panicking.rs:145:5
   3: poll<futures_util::stream::stream::fuse::Fuse<reth_payload_builder_primitives::events::BuiltPayloadStream<tempo_payload_types::TempoPayloadTypes>>>
             at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-util-0.3.31/src/stream/stream/select_next_some.rs:32:9
   4: {closure#1}<reth_node_api::node::FullNodeTypesAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>, reth_provider::providers::blockchain_provider::BlockchainProvider<reth_node_types::NodeTypesWithDBAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>>>>, reth_node_builder::components::builder::ComponentsBuilder<reth_node_api::node::FullNodeTypesAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>, reth_provider::providers::blockchain_provider::BlockchainProvider<reth_node_types::NodeTypesWithDBAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>>>>, tempo_node::node::TempoPoolBuilder, reth_node_builder::components::payload::BasicPayloadServiceBuilder<tempo_node::node::TempoPayloadBuilderBuilder>, reth_node_ethereum::node::EthereumNetworkBuilder, tempo_node::node::TempoExecutorBuilder, tempo_node::node::TempoConsensusBuilder>, tempo_node::node::TempoAddOns<reth_node_builder::builder::states::NodeAdapter<reth_node_api::node::FullNodeTypesAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>, reth_provider::providers::blockchain_provider::BlockchainProvider<reth_node_types::NodeTypesWithDBAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>>>>, reth_node_builder::components::Components<reth_node_api::node::FullNodeTypesAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>, reth_provider::providers::blockchain_provider::BlockchainProvider<reth_node_types::NodeTypesWithDBAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>>>>, reth_network::network::NetworkHandle<reth_eth_wire_types::primitives::BasicNetworkPrimitives<tempo_primitives::TempoPrimitives, tempo_primitives::transaction::envelope::TempoTxEnvelope, reth_eth_wire_types::broadcast::NewBlock<alloy_consensus::block::Block<tempo_primitives::transaction::envelope::TempoTxEnvelope, tempo_primitives::header::TempoHeader>>>>, tempo_transaction_pool::tempo_pool::TempoTransactionPool<reth_provider::providers::blockchain_provider::BlockchainProvider<reth_node_types::NodeTypesWithDBAdapter<tempo_node::node::TempoNode, alloc::sync::Arc<reth_db::implementation::mdbx::DatabaseEnv, alloc::alloc::Global>>>>, tempo_evm::TempoEvmConfig, tempo_consensus::TempoConsensus>>, tempo_node::rpc::TempoEthApiBuilder, tempo_node::node::TempoEngineValidatorBuilder, reth_node_builder::rpc::BasicEngineValidatorBuilder<tempo_node::node::TempoEngineValidatorBuilder>, tower_layer::identity::Identity>>
             at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.49.0/src/macros/select.rs:707:49
2026-02-09T11:32:45.477620Z  INFO Using RPC consensus client: wss://rpc.presto.tempo.xyz
2026-02-09T11:32:46.012383Z ERROR shutting down due to error

7. After container restart few times in log i see

2026-02-09T11:36:04.015303Z  INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/tempo
2026-02-09T11:36:04.017744Z  INFO Starting Tempo version="1.1.0 (2fe3367)"
2026-02-09T11:36:04.017829Z  INFO Opening database path="/root/.local/share/reth/tempo/db"
2026-02-09T11:36:04.066910Z  INFO Configuration loaded path="/root/.local/share/reth/tempo/reth.toml"
2026-02-09T11:36:04.067308Z  INFO Healing static file inconsistencies.
2026-02-09T11:36:04.288850Z  INFO Verifying storage consistency.
2026-02-09T11:36:04.289321Z  INFO Database opened
2026-02-09T11:36:04.289391Z  INFO Storage settings settings=Some(StorageSettings { receipts_in_static_files: false, transaction_senders_in_static_files: false, storages_history_in_rocksdb: false, transaction_ha
sh_numbers_in_rocksdb: false, account_history_in_rocksdb: false, account_changesets_in_static_files: false })
2026-02-09T11:36:04.289615Z  INFO Starting metrics endpoint at 127.0.0.1:9000
2026-02-09T11:36:04.290087Z  INFO 
Post-merge hard forks (timestamp based):
- Genesis                          @0
- T0                               @0
2026-02-09T11:36:04.306099Z  INFO Transaction pool initialized
2026-02-09T11:36:04.321020Z  INFO P2P networking initialized enode=enode://4f33af20e2599613574040e03bc08f37f0fce05e8a76b907e0a5e956f39ba11c90888a6ad0673a10f719e19893e406507d5b70179788a1fd6842f4ceeac143a1@0.0.0.
0:30303
2026-02-09T11:36:04.321310Z  INFO StaticFileProducer initialized
2026-02-09T11:36:04.321783Z  INFO Pruner initialized prune_config=PruneConfig { block_interval: 5, segments: PruneModes { sender_recovery: None, transaction_lookup: None, receipts: None, account_history: None, 
storage_history: None, bodies_history: None, merkle_changesets: Distance(128), receipts_log_filter: ReceiptsLogPruneConfig({}) } }
2026-02-09T11:36:04.322237Z  INFO Consensus engine initialized
2026-02-09T11:36:04.322254Z  INFO Engine API handler initialized
2026-02-09T11:36:04.328470Z  INFO RPC auth server started url=127.0.0.1:8551
2026-02-09T11:36:04.328739Z  INFO RPC IPC server started path=/tmp/reth.ipc
2026-02-09T11:36:04.328748Z  INFO RPC HTTP server started url=0.0.0.0:8545
2026-02-09T11:36:04.328943Z  INFO Starting consensus engine
2026-02-09T11:36:04.328969Z  INFO Using RPC consensus client: wss://rpc.presto.tempo.xyz
2026-02-09T11:36:04.855587Z ERROR shutting down due to error

[Nich01asFox]

@ahmedbolanta
i also try run 1.0.0 version

1. Delete all
2. Download snapshot by run
   docker run -d -v tempo_cache:/root/.cache/reth -v tempo_local:/root/.local/share/reth --name tempo-snap ghcr.io/tempoxyz/tempo:1.0.0 download -u https://tempo-node-snapshots.tempoxyz.dev/tempo-4217-3928501-1770613222.tar.lz4
3. correct image version and run compose
4. get in logs

2026-02-09T11:50:38.475048Z  INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/tempo
2026-02-09T11:50:38.476336Z  INFO Starting Tempo version="1.0.0 (9ad04e2)"
2026-02-09T11:50:38.476408Z  INFO Opening database path="/root/.local/share/reth/tempo/db"
2026-02-09T11:50:38.536677Z  INFO Configuration loaded path="/root/.local/share/reth/tempo/reth.toml"
2026-02-09T11:50:38.537475Z  INFO Healing static file inconsistencies.
2026-02-09T11:50:38.700376Z  INFO Verifying storage consistency.
2026-02-09T11:50:38.700553Z  INFO Database opened
2026-02-09T11:50:38.700613Z  INFO Storage settings settings=Some(StorageSettings { receipts_in_static_files: false, transaction_senders_in_static_files: false, storages_history_in_rocksdb: false, transaction_hash_numbers_in_rocksdb: false, account_history_in_rocksdb: false, account_changesets_in_static_files: false })
2026-02-09T11:50:38.700703Z  INFO Starting metrics endpoint at 127.0.0.1:9000
2026-02-09T11:50:38.700961Z  INFO 
Post-merge hard forks (timestamp based):
- Genesis                          @0
- T0                               @0
2026-02-09T11:50:38.711367Z  INFO Transaction pool initialized
2026-02-09T11:50:38.727018Z  INFO P2P networking initialized enode=enode://8a8cfa4e39ae6720000a896e232f28e519da4336c58a0a8d59ad5e2f4dcb32809c4467a1a9bf11926862cc847be790dc1bd615f2cff02c855a063b057a4534b8@0.0.0.0:30303
2026-02-09T11:50:38.727222Z  INFO StaticFileProducer initialized
2026-02-09T11:50:38.727676Z  INFO Pruner initialized prune_config=PruneConfig { block_interval: 5, segments: PruneModes { sender_recovery: None, transaction_lookup: None, receipts: None, account_history: None, storage_history: None, bodies_history: None, merkle_changesets: Distance(128), receipts_log_filter: ReceiptsLogPruneConfig({}) } }
2026-02-09T11:50:38.728089Z  INFO Consensus engine initialized
2026-02-09T11:50:38.728104Z  INFO Engine API handler initialized
2026-02-09T11:50:38.734170Z  INFO RPC auth server started url=127.0.0.1:8551
2026-02-09T11:50:38.734355Z  INFO RPC IPC server started path=/tmp/reth.ipc
2026-02-09T11:50:38.734364Z  INFO RPC HTTP server started url=0.0.0.0:8545
2026-02-09T11:50:38.734742Z  INFO Starting consensus engine
2026-02-09T11:50:38.734784Z  INFO Using RPC consensus client: wss://rpc.presto.tempo.xyz
2026-02-09T11:50:39.261431Z ERROR shutting down due to error
Error: execution node failed

Caused by:
   0: failed launching execution node
   1: HTTP error: 401 Unauthorized
   2: HTTP error: 401 Unauthorized

[ahmedbolanta]

Hi @Nich01asFox,

Thanks for the detailed follow-up. The 401 Unauthorized error makes sense now — I checked the v1.1.0 release notes and found the issue.

Since v1.0.0, testnet nodes must use --chain moderato. The old andantino chainspec was removed. Your compose command is missing this flag, so the node defaults to the wrong chain and gets rejected by the consensus layer.

Fix: Add --chain moderato to your compose command:

command: node --follow --chain moderato --port 30303 --discovery.addr 0.0.0.0 --discovery.port 30303 --http

Then do a clean restart:

docker compose down
docker volume rm tempo_local
docker compose up -d

That should get you syncing. Let me know how it goes!

[Nich01asFox]

Hi @ahmedbolanta , yes , with --chain moderato node work as expected. Thank you for help!