Startup And Readiness
Symptoms
Section titled “Symptoms”/healthzreturnsokbut/readyzfails.- The process exits during startup.
- systemd restarts
oriel.service. - Compose reports
orielunhealthy.
Checks
Section titled “Checks”Run:
oriel --config /etc/oriel/oriel.toml doctorCheck service logs:
journalctl -u oriel.service -n 200For compose:
docker compose logs orieldocker compose logs oriel-migrateCommon Causes
Section titled “Common Causes”| Cause | Signal | Fix |
|---|---|---|
| PostgreSQL unreachable | ORL-5003 or startup connection error | Fix metadata.dsn, network, credentials, or database state. |
| ClickHouse unreachable | ORL-5001 | Fix clickhouse.dsn, network, credentials, or ClickHouse state. |
| Valkey unreachable | ORL-5005 or startup connection error | Fix valkey.dsn, network, credentials, or Valkey state. |
| Schema mismatch | ORL-5002 on /readyz | Run oriel migrate up with the service config. |
| Plaintext non-loopback bind | Startup error from listener guard | Configure TLS, bind loopback, or intentionally set server.insecure = true. |
| Bad OIDC config | ORL-3004 | Fix provider slug, icon, group map, public_url, or redirect_url. |
Recovery
Section titled “Recovery”Prefer this order:
- Fix configuration and dependencies.
- Run
oriel doctor. - Run
oriel migrate status. - Run
oriel migrate upif pending migrations exist. - Restart Oriel.
Avoid repeated restarts before dependency and schema checks are clean.