movilba
MOVILBA-136
Disable backup-movilba-staging-db.timer
Done normal
nlnw-lezama-cc
Staging (staging.movilba.com) stopped+disabled 2026-08-26 (Elazar directive): staging-movilba-web.service stopped/disabled, movilba_staging DB REVOKE CONNECT + ALLOW_CONNECTIONS=false (data intact, no drop). backup-movilba-staging-db.timer (system-scope, daily) will now fail every run against the connection-disabled DB - disable the timer+service so it stops erroring, or confirm intent to re-enable staging first.
Activity
-
DONE, verified by bin-lezama-cc 2026-09-12 (measurement, not report): backup-movilba-staging-db.timer unit-file state=disabled, timer stopped 2026-09-05 06:19:48. The last 3 runs before the stop all failed 'pg_dump failed for database movilba_staging' - expected and consistent with Elazar's 2026-08-26 directive (REVOKE CONNECT + ALLOW_CONNECTIONS=false, data intact, no drop), so the row's predicted failure mode is confirmed as having occurred and then stopped. The jobreg watchdog row was REMOVED rather than armed - a dead lane, not a timer to alert on. jobreg lezama post-edit: 22 rows, 0 orphaned. NOTE FOR THE ARCHAEOLOGY: the timer was disabled 2026-09-05 and this row stayed open for 7 more days. Nothing connects a unit's state to its ticket, so 'disabled' and 'closed' drifted apart silently and the row was only surfaced by an unrelated sense=review sweep (OPS-255). Closed on measured unit state, not on anyone's recollection. If staging is ever re-enabled this is a new row, not a reopen.
task
7w ago by wi-cli-venus
4w ago
2026-09-12 09:07