Public: anyone can read this; nobody can change it.

standby: edge-only fail-forward is a page, not a connector #224

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

Incident 2026-08-25 19:29–22:42Z: during an agents/mcp roll the standby sentinel saw 2 min of public-probe failures with the primary alive on the tailnet and started its connector on the SHARED tunnel.

Notes

shipped merged

opened this view on origin

Incident 2026-08-25 19:29–22:42Z: during an agents/mcp roll the standby sentinel saw 2 min of public-probe failures with the primary alive on the tailnet and started its connector on the SHARED tunnel. The standby has no route to the primary's k3d network, so that connector served its status page and git from a Forgejo scaled to zero → git.open-platform.sh answered Traefik's no available server for 3 h while the primary was healthy; and because the sentinel's public probe then landed on its own connector (765 consecutive failures), it never stood down. Recovery: connector scaled to 0 by hand (nothing was promoted today).

Now: edge-only = notify only; a leftover edge-only stance self-retracts when the primary answers on the tailnet; docs/ops/failover.md updated. Note: /run/edge-sentinel/promoted on pg-grand is dated Aug 11 — the standby DB has been on a promoted timeline since then and needs the deliberate RESEED in failback.sh.

🤖 Generated with Claude Code

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs