Say why the data store couldn't be opened, with an exit code per case #472

Merged
jcoffey-dev merged 1 commits from feat/startup-data-store-errors into main 2026-11-19 04:33:41 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev a00040289c Say why the data store couldn't be opened, with an exit code per case
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 11m28s
Every start-up failure to open the data store exited with 1 and the
driver's own words, so a supervisor, a Kubernetes pre-flight check or a
person reading pod status couldn't tell a database that's down from a
wrong password. Now each case has its own first words and exit code
(sysexits.h), and a one-line hint:

  78  data store: bad configuration    settings file, secret files, database name
  69  data store: unreachable          refused, unknown host, timed out, starting, full
  77  data store: credentials refused  wrong user or password, missing permission
  76  data store: TLS failed           handshake failed
  1   data store: error                anything else

PostgreSQL errors are told apart fully; other stores report bad
configuration and otherwise 1. K-S6.
2026-11-18 21:04:24 -07:00