hiveloom doctor
Inspects the on-disk state of a Hiveloom installation and prints a list of
findings. Unlike health and status, doctor runs against the data
directory directly — it does not require the service to be running.
Synopsis
hiveloom doctor [OPTIONS]Options
| Flag | Default | Description |
|---|---|---|
--data-dir <DATA_DIR> | /var/lib/hiveloom | Data directory to inspect. |
--json | — | JSON output. |
Examples
Default install:
hiveloom doctorCustom data directory:
hiveloom doctor --data-dir /srv/hiveloomPipe into a diagnostics tarball:
hiveloom doctor --json > doctor.jsonWhat it checks
- Data directory exists with sensible permissions.
- Platform DB (
platform.db) is openable and passesPRAGMA integrity_check. - Master key file is present and readable by the running user.
- Per-tenant databases exist for every active tenant in the platform DB.
- WAL/SHM files are not orphaned from a prior crash.
Each finding is tagged ok, warn, or fail. Run doctor first when
/healthz is returning 503 and you don’t yet know whether
the issue is config, data, or runtime.