Troubleshooting: Run a node

You see Unindex transactions.

This is expected behavior. You'll see this when your node removes old txlookup indices. This is emitted from the base Geth node, so you'd see the same output from a mainnet Geth node.

You see Head state missing, repairing.

This is usually because your node shuts down ungracefully. In most cases, it will recover in a few minutes, but if it not, you may have to re-sync your node. Remember to shut down your node gracefully with the following command: docker stop —time=1800 $(docker ps -aq).

Your Arbitrum node can’t connect to your parent chain node on localhost:8545

You specified your snapshot file path via the --init.url parameter, but the snapshot file isn't found.

You get 403 errors from the feed URL.

You see latest assertion not yet in our node

You see "Post "xxx_url": context deadline exceeded"

You see Resuming state snapshot generation

You see track-block-metadata-from is set but blockMetadata fetcher is not enabled.

You started the node with --node.transaction-streamer.track-block-metadata-from set to a non-zero block but did not enable the blockMetadata fetcher. The node will still run, but blockMetadata won't be backfilled. Either remove the flag, or enable the fetcher with --node.block-metadata-fetcher.enable—and when enabling the fetcher you'll typically also need to set --node.block-metadata-fetcher.source.url to point at a node that serves block metadata.

You see error reading inbox err="sequencer batches out of order; after batch A got batch B”

You see error reading inbox err="failed to get previous message for pos x: leveldb: not found”

You see Failed to load snapshot err="head doesn't match snapshot: have a, want b”

You see failed to get blobs: expected at least six blobs for slot [slot_number] but only got 0

This often happens when you connect to a beacon chain endpoint while the blob you are querying is expired. To resolve this error, connect to a beacon endpoint that supports historical blob data (see List of Ethereum beacon chain RPC providers ).

You see P2P server will be useless, neither dialing nor listening

You see Getting file info dir=<path>/machines error="stat <path>/machines: no such file or directory".

Nitro is checking one of the expected locations for WASM machine artifacts, but that particular machines/ directory does not exist. This warning can be harmless if Nitro finds the required machine artifacts in another location. If it is followed by validation or WASM module-root errors, make sure you're running a supported/current Nitro image for your chain, and that the image or mounted machines/ directory contains artifacts matching the chain's onchain WASM module root. If you're using an older Docker image, upgrade to a newer Nitro release; if you're building or running from source, mount or download the matching machine artifacts for that Nitro version/module root.

You see broadcaster queue jumped positions queuedMessages=N expectedNextIdx=M.

The feed delivered messages out of the expected order; the node skipped ahead in its broadcast queue. This typically self-heals as later messages arrive. If it persists, check your feed URL connectivity or try a fallback feed via --node.feed.input.url.

You see Compression was not negotiated when connecting to feed server, non-critical: node will continue without compression.

You see readData returned EOF url=wss://...feed... opcode=0.

You see error reading inbox err="previous delayed accumulator mismatch for message N".

You see error reading inbox err="unexpected delayed sequence number N, expected M".

You see Trie prefetcher failed opening storage trie root=... err="missing trie node ...".

Your local state database is inconsistent—typically caused by an ungraceful shutdown or by enabling --init.recreate-missing-state-from on a non-archive node. Restart without pruning; if the node still can't recover, re-sync from a recent official snapshot.

You see error reading inbox err="...pebble: not found" (same root cause as the leveldb: not found case above; different database backend).

Same root cause as the leveldb: not found case above: your local DB is missing a message it expected to have. Use --init.reorg-to-message-batch x-1 to roll back to before the missing index, or re-sync from a snapshot.

You see no contract code at given address

You see staker: error checking latest staked err="latest assertion of x: globalstate not in chain: count a hash b expected c, sendroot d expected f"

You see disabling L1 bound as batch posting message is close to the maximum delay blockNumber or batch is within reorg resistance margin from layer 1 minimum block or timestamp bounds

It indicates that there has been an issue with batch posting on the network. This could occur if your batch poster didn't post a batch for an extended period. Common reasons include the node being shut down inadvertently or the batch poster running out of funds, leading to no new blocks being produced or posted by the batch poster.
To resolve this, If re-org doesn’t matter, you can just start the batch poster with --node.batch-poster.reorg-resistance-margin=0 and node.batch-poster.l1-block-bound to ignore, If it does, you'd want to modify the time bounds on the sequencer inbox to allow the sequencer to post a batch containing the transactions with the old timestamp

You see on-chain WASM module root did not match with any of the allowed WASM module roots

You see error acting as staker

You see wrong msgIdx got X expected Y.

The transaction streamer received a message whose index doesn't match the next expected one—your node's local DB is behind or ahead of the sequencer feed. Restart the node; if the gap persists, re-sync from a snapshot or use --init.reorg-to-message-batch to roll back to a known-good index.

You see error reading inbox err="...header not found" or header for hash not found.

You see accumulator not found or delayed accumulator not found for index N.

You see error initializing database err="found N unexpected files in database directory, including: ...".

The data directory you pointed nitro at already contains files that don't belong to a fresh DB. Either empty the directory before init, or point --persistent.chain at a fresh path and extract your snapshot there.

You see error validating feed signature error="signature not verified: signer ..." sequence number=N.

A feed message was signed by an address that is not in your allowed signer list. Check that --node.feed.input.verify.allowed-addresses includes the expected sequencer feed signer for your chain; for Arbitrum One/Sepolia this should be the official feed signer published in the docs.

You see no connected feed or no connected feed on startup.

The broadcast client failed to connect to any feed URL you configured. Check network/firewall rules for outbound WebSocket connections, verify the feed URLs in --node.feed.input.url are reachable, and confirm you can curl them from the node host.