nautechsystems/nautilus_trader · error · anyhow::Error

Failed to seed chain table: {e}

Error message

Failed to seed chain table: {e}

What it means

This error is returned when the SQLx upsert (INSERT ... ON CONFLICT) into the chain table fails while seeding a chain's metadata (chain_id, name). It wraps the underlying sqlx::Error, so the real cause (connectivity, permissions, constraint) is in the chained source.

Source

Thrown at crates/adapters/blockchain/src/cache/database.rs:363

    /// # Errors
    ///
    /// Returns an error if the database operation fails.
    pub async fn seed_chain(&self, chain: &Chain) -> anyhow::Result<()> {
        sqlx::query(
            "
            INSERT INTO chain (
                chain_id, name
            ) VALUES ($1,$2)
            ON CONFLICT (chain_id)
            DO NOTHING
        ",
        )
        .bind(chain.chain_id as i32)
        .bind(chain.name.to_string())
        .execute(&self.pool)
        .await
        .map(|_| ())
        .map_err(|e| anyhow::anyhow!("Failed to seed chain table: {e}"))
    }

    /// Creates a table partition for the block table specific to the given chain
    /// by calling the existing PostgreSQL function `create_block_partition`.
    ///
    /// # Errors
    ///
    /// Returns an error if the database operation fails.
    pub async fn create_block_partition(&self, chain: &Chain) -> anyhow::Result<String> {
        let result: (String,) = sqlx::query_as("SELECT create_block_partition($1)")
            .bind(chain.chain_id as i32)
            .fetch_one(&self.pool)
            .await
            .map_err(|e| {
                anyhow::anyhow!(
                    "Failed to call create_block_partition for chain {}: {e}",
                    chain.chain_id
                )

View on GitHub (pinned to 18893faf8b)

Solutions

1. Inspect the wrapped {e} source for the exact sqlx error
2. Verify the database is reachable and migrations ran (chain table exists)
3. Check the DB user has INSERT/UPDATE privileges on the chain table
4. Retry seeding once connectivity is confirmed

Example fix

// before
let db = CacheDatabase::connect(&url).await?;
// after: fail fast with context if seeding fails
let db = CacheDatabase::connect(&url).await
    .map_err(|e| anyhow::anyhow!("cache DB unreachable, cannot seed chain: {e}"))?;

// verify migrations applied before seeding
let applied: Vec<(String,)> = sqlx::query_as("SELECT version FROM _sqlx_migrations")
    .fetch_all(&pool).await?;
if applied.len() < EXPECTED_MIGRATIONS {
    return Err(anyhow::anyhow!("database not migrated; cannot seed chain table"));
}

match db.seed_chain(&chain).await {
    Ok(()) => (),
    Err(e) if e.to_string().contains("connect") => {
        // transient connectivity at startup: retry once
        tokio::time::sleep(Duration::from_secs(3)).await;
        db.seed_chain(&chain).await?;
    }
    Err(e) => return Err(e),
}

When it happens

Trigger: seed_chain (or the method containing this bind/execute) is called during CacheDatabase setup and the INSERT into the chain table errors — connection failure, insufficient privileges, or a constraint violation on chain_id/name.

Common situations: Wrong DATABASE_URL / database not migrated; the DB user lacks INSERT privilege on the chain table; transient connection loss at adapter startup.

Related errors

• Failed to call create_block_partition for chain {}: {e}
• Failed to call create_token_partition for chain {}: {e}
• Failed to get block info for chain {}: {}
• Failed to insert into block table: {e}
• Failed to batch insert into block table: {e}

AI-assisted analysis of nautechsystems/nautilus_trader@18893faf8b (2026-09-08). Data as JSON: /api/errors/723ee2944973abee. Report an issue: GitHub.