linera-io/linera-protocol · error · LocalNodeError

The local node doesn't have an active chain {0}

Error message

The local node doesn't have an active chain {0}

What it means

Error "The local node doesn't have an active chain {0}" thrown in linera-io/linera-protocol.

Source

Thrown at linera-core/src/client/chain_client/mod.rs:763

            .map_err(LocalNodeError::from)?)
    }

    /// Obtains the committee for the latest epoch on the admin chain.
    #[instrument(level = "trace")]
    pub async fn admin_committee(&self) -> Result<(Epoch, Arc<Committee>), LocalNodeError> {
        self.client.admin_committee().await
    }

    /// Obtains the identity of the current owner of the chain.
    ///
    /// Returns an error if we don't have the private key for the identity.
    #[instrument(level = "trace")]
    pub async fn identity(&self) -> Result<AccountOwner, Error> {
        let Some(preferred_owner) = self.preferred_owner else {
            return Err(Error::NoAccountKeyConfigured(self.chain_id));
        };
        let manager = self.chain_info().await?.manager;
        ensure!(
            manager.ownership.is_active(),
            LocalNodeError::InactiveChain(self.chain_id)
        );
        let fallback_owners = if manager.ownership.has_fallback() {
            self.local_committee()
                .await?
                .account_keys_and_weights()
                .map(|(key, _)| AccountOwner::from(key))
                .collect()
        } else {
            BTreeSet::new()
        };

        let is_owner = manager
            .ownership
            .can_propose_in_multi_leader_round(&preferred_owner)
            || fallback_owners.contains(&preferred_owner);

View on GitHub (pinned to 6c226ddcb3)

Solutions

  1. Activate the chain locally first: run `linera open-chain` or `linera assign` (or `linera sync` for an existing owned chain) so chain {0} becomes active in the wallet.
  2. Confirm the default chain is set correctly with `linera wallet show` and switch with `linera set-default` if needed.
  3. Check for typos in the chain id argument passed to the command.

When it happens

Trigger: An operation is attempted on a chain that is not active in the local node's state view.

Common situations: Querying or proposing a block for a chain the node has not opened or that was removed from local storage.


AI-assisted analysis of linera-io/linera-protocol@6c226ddcb3 (2026-08-22). Data as JSON: /api/errors/cba5d573138aedbd. Report an issue: GitHub.