diff --git a/docs/deployment/deployment-records/2026-11-20-prod-cluster-config.md b/docs/deployment/deployment-records/2026-11-20-prod-cluster-config.md index c8ef7960..c382241c 100644 --- a/docs/deployment/deployment-records/2026-11-20-prod-cluster-config.md +++ b/docs/deployment/deployment-records/2026-11-20-prod-cluster-config.md @@ -90,3 +90,17 @@ Its Galaxy browse needs #60. - Connection: `data-connection delete --id 1`, then `deploy artifacts --site-id 1`. - Site: `site delete --id 1` (the site nodes go back to unregistered heartbeats). - Key: `apikey revoke-key --key-id scadabridge-prod` on each box. On vp04 you can instead restore `gateway-auth.db.bak-20261120-prod-keycopy` with the service stopped. + +## 2026-11-20 22:22Z: connection re-pointed to the PAR gateways (owner: "the par mxgw on the par scadabridge instances", chose "Re-point to PAR only") + +- `data-connection update --id 1`: primary `http://10.201.75.86:5120` (par-vp03), backup `http://10.201.75.87:5120` + (par-vp04), same `scadabridge-prod` token and settings, retry 3. Config files 0600 in the scratchpad, deleted after use. + CLI built from a detached `2e0ce81e` worktree (assembly `scadabridge.dll`). +- `deploy artifacts --site-id 1` → deployment `2264d02f4b21450fa1ac61ad8161fb35`, success. par-vp03 logged + "Reconfigured DCL connection MxGateway ... in place" (no restart), then `Connect failed: Error connecting to subchannel` + retries. **Expected: mxgw is not installed on the PAR boxes** (held for WinPlatform, plan Q3). Site-par has no working + gateway until then; the connection retries (WRN log lines) and fails over between the two PAR endpoints. +- **When mxgw is installed on par-vp03/04:** use the same `MxGateway__ApiKeyPepper` (Keychain `zb-prod/mxgw-pepper`) and + copy vp03's `gateway-auth.db` (service stopped) so the `scadabridge-prod` token is valid there; then the connection + comes up on its own. Install script fix first: mxaccessgw#234. +- Rollback to the app-box gateways: the same `update` with `10.220.153.205:5120` / `10.220.153.210:5120`, then `deploy artifacts --site-id 1`.