api health: duckdb reports "down" — wrong path in stack.toml #130

Closed
opened 2026-03-23 22:43:58 +00:00 by kert · 0 comments
Owner

Problem

GET /health returns {"name":"duckdb","status":"down","detail":"file not found"}.

The health check calls path("db.aco") which resolves to notebooks/aco.duckdb per stack.toml. But:

  • The actual file is at data/aco.duckdb (3.2 GB)
  • notebooks/aco.duckdb is just a symlink to ../data/aco.duckdb
  • The api container only mounts ./data:/app/data — the symlink target resolves, but the symlink itself is not in the container

Fix

Change stack.toml [db] aco from notebooks/aco.duckdb to data/aco.duckdb to match the actual file location and the volume mount.

## Problem `GET /health` returns `{"name":"duckdb","status":"down","detail":"file not found"}`. The health check calls `path("db.aco")` which resolves to `notebooks/aco.duckdb` per `stack.toml`. But: - The actual file is at `data/aco.duckdb` (3.2 GB) - `notebooks/aco.duckdb` is just a symlink to `../data/aco.duckdb` - The api container only mounts `./data:/app/data` — the symlink target resolves, but the symlink itself is not in the container ## Fix Change `stack.toml` `[db] aco` from `notebooks/aco.duckdb` to `data/aco.duckdb` to match the actual file location and the volume mount.
kert closed this issue 2026-03-23 22:46:36 +00:00
Sign in to join this conversation.