opschain admin status
Included from Basic tier
One-look server health: the admin-gated v2 SystemService.GetSystemStatus read,
showing the server's status, version and commit, which replica answered (its
id, leadership, held shard count and whether it is draining), the store's
ping health (the store: line — ok, or the ping's error text; see
opschain docs resources/admin_status), the directory provider's health as this replica has observed it (the
ldap: line — configured, last successful bind, last error; see
opschain docs resources/admin_status), a ready/leased queue summary, and —
on a multi-replica fleet — every scheduler replica with its heartbeat age
and whether the fleet still counts it as live (LIVE: a heartbeat inside
the 15 s staleness window; a replica that died without a goodbye keeps its
membership row, LIVE false, until the leader reaps it after the
replica-retention window — its shards, leadership and run drives moved to
its peers at the staleness boundary, see opschain docs dispatch). Use it as
the first probe when "is the server up, and who is leading?" is the
question; admin queue is the deeper dispatch view.
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN). |
Like every admin verb, this command rides your opschain login session by
default, with the admin-token lanes as the automation fallback.
-o json|yaml prints the raw status document instead of the rendered lines.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Status fetched. |
| 1 | Request failed, non-200 response, or the token was rejected. |
| 2 | Usage error — missing server or token. |
Named errors
this command needs a login or an admin token — run 'opschain login', pass --auth-token, set OPSCHAIN_ADMIN_TOKEN, or store one with 'opschain admin login'— exit 2.the server rejected the credential — run 'opschain login' again, or check the admin token— HTTP 401 (exit 1).the server answered <code>: <message>— any other refusal (exit 1).
Examples
opschain admin status --server https://ops.example.com
status: ok
version: 2026.10.1 (4f3c2d1)
replica: replica-a (leader: true, shards: 4, draining: false)
store: ok
ldap: configured, last error at 2026-10-15T03:12:44Z: ldap directory unreachable at 127.0.0.1:1389: dial tcp 127.0.0.1:1389: connect: connection refused
queue: 3 ready, 2 leased
REPLICA HEARTBEAT AGE LIVE
replica-a 0.4s true
replica-b 1.2s true
replica-c 171.6s false
replica-c here died without a goodbye: its row stays listed (and
LIVE false) until the leader's reaper retires it, while its work moved to
replica-a/replica-b within the staleness window.
See also
opschain docs cli/admin-queue— the queue and lease detail behind the one-line summary.opschain docs cli/admin-changes-active— what is actually running.