frankie (pg standby) needs db-perms.sh re-run when reachable #4

Open
opened 2026-07-02 06:28:50 +00:00 by grenade · 0 comments
Owner

frankie.hanzalova.internal was unreachable (no route to host 10.6.0.70) when the app-owned pg_ident.conf.d/moments.conf migration ran against magrathea on 2026-07-02 (#3).

The standby therefore still has the legacy host-named layout — and critically never received the frootmig.kosherinata.internal → moments_rw mapping at all, so a failover today would lock the worker out.

When frankie is back: run script/db-perms.sh from a workstation; it converges both pg hosts in one idempotent pass (migrates legacy lines into moments.conf, adds missing mappings, reloads postgres only if changed).

frankie.hanzalova.internal was unreachable (`no route to host 10.6.0.70`) when the app-owned `pg_ident.conf.d/moments.conf` migration ran against magrathea on 2026-07-02 (#3). The standby therefore still has the legacy host-named layout — and critically never received the `frootmig.kosherinata.internal → moments_rw` mapping at all, so a failover today would lock the worker out. When frankie is back: run `script/db-perms.sh` from a workstation; it converges both pg hosts in one idempotent pass (migrates legacy lines into `moments.conf`, adds missing mappings, reloads postgres only if changed).
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: grenade/moments#4