opschain server migrate status
Included from Basic tier
Reports the migration integrity verdict directly from the configured
database — the same verification server boot runs, computed without any
server process. Read-only: safe to run anytime, including against the
database of a server that is up. A clean ledger prints one OK line and
exits 0; any finding prints every finding plus the remedy and exits 1.
The finding kinds (mismatch, hole, unrecorded) and output shape are
identical to opschain admin database migrations status.
The store comes from the server host's own config.yaml (resolved via
--home); a missing config, an unreachable database, or a database with
no migration history at all each refuse with a named error instead of a
verdict.
Under -o json / -o yaml the verdict document is printed verbatim; the
exit code still reflects the verdict.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The ledger verifies clean. |
| 1 | The verdict carries findings, the database was unreachable, or it holds no migration history. |
| 2 | Usage error — no config.yaml at the resolved server home. |
Examples
opschain server migrate status
opschain server migrate status --home /var/lib/opschain -o json
See also
opschain docs cli/server-migrate-list— the per-version view behind the verdict.opschain docs cli/server-migrate-up— apply what is pending once the cause is fixed.