⚠️ Homebrew support is being deprecated. Solo will stop publishing updates to Homebrew after August 31, 2026. Install via npm install -g @hiero-ledger/solo@latest instead. See System Readiness for full install instructions.

SOLO-3097

NodeRestoreStatusMismatchSoloError — Component

NodeRestoreStatusMismatchSoloError

CodeSOLO-3097
CategoryComponent
OwnershipUser
RetryableNo

Description

Thrown when a --state-file restore settles some nodes into ACTIVE and others into FREEZE_COMPLETE instead of all nodes reaching the same terminal status; the message lists each node alias with the status it reached. checkAllNodesAreActiveOrFrozen waits for every node to reach one of those two statuses and only skips the ACTIVE-only follow-up work when every node came up frozen, so a mixed result means the nodes disagree about whether the restored snapshot replays back into a freeze — continuing would run the ACTIVE-only checks against a node that can never become ACTIVE without a fresh start, which only fails after burning the full activeness timeout.

Troubleshooting Steps

  1. Every restored node must reach the same status, ACTIVE or FREEZE_COMPLETE
  2. Check pod status for the node(s) that disagree: kubectl get pods -n -l solo.hedera.com/node-name=
  3. Review node logs: kubectl logs -n -l solo.hedera.com/node-name=