admin
9c69b3ff07
gates / gates (push) Successful in 27s
Evidence off the machine at the end of the phases that produced it (R-320). Teardown follows. PHASE 2 — the two database engines, through the REAL Update button: - MariaDB 11.6 -> 12.3 on nextcloud: PROVEN, and pressed through the button for the first time. All four SPIKE-r459 observables: the datadir's own record moved 11.6.2 -> 12.3.3; the engine itself says "already upgraded ... no need to run mariadb-upgrade again"; the entrypoint says "Major version upgrade detected ... Check required!" and then STARTED and FINISHED it (not the `skipped due to $MARIADB_AUTO_UPGRADE` line R-459 feared); and the engine took its own pre-upgrade backup, 631 905 B. The seeded Nextcloud account read back. - PostgreSQL 16 -> 17 on docmost: FAILED exactly as R-463 predicted and nobody had measured. 5.1 s to held; the pin named 17 while nothing ran; the restore brought it back in 29.1 s. The engine's REFUSAL LINE was destroyed by failAndHold before any probe could read it, so it was REPRODUCED INDEPENDENTLY with a control on every step (R-320). PHASE 3 — the bad days. B1 produced THE UNATTENDED HOLD, which this project has never had: the caller pressed once with nobody watching, the app held after 312.9 s, and passes 2 and 3 pressed nothing. B2 put the pin back on a pull failure in 1.0 s. B3 refused `busy` six times. B4 showed there is NO single-flight — 5 of 5 updates ran at once and all ended honest. B5 cut the power in `backing-up` and the box recovered itself and said so. B7 refused under the 2 GB floor. B9 found R-458's risk narrower than the row states. PHASE 4 — every badge on the box is TRUE, and the held app answers all four of Q4's questions. FINDINGS, five new and three corrections to existing rows. The one that matters: R-618 is P1 — two templates name a health probe the app does not answer, and because the guarded update waits on that same probe, a SUCCESSFUL update ends by STOPPING a working app. Measured: tandoor served HTTP 200 on the new version at four samples across five minutes and was then stopped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
18 lines
929 B
Bash
Executable File
18 lines
929 B
Bash
Executable File
#!/bin/bash
|
|
# The leftovers, in value order. Run AFTER phase2_redo.sh, BEFORE the teardown.
|
|
cd /mnt/5_hdd/felhom.eu/git/felhom.eu/documentation/audits/update-night-2026-09-21 || exit 1
|
|
step() { echo; echo "############################################## $(date +%H:%M:%S) $*"; }
|
|
|
|
step "L1 wger — the LAST unmeasured candidate in R-618, and the one that would close it"
|
|
timeout 2700 python3 measure_wger.py
|
|
|
|
step "L2 B5 retry — the cut in safety-dump, with a REAL pending edge this time"
|
|
timeout 2700 python3 phase3_b5.py knob backup_max_age 24h
|
|
timeout 2700 python3 phase3_b5.py privatebin paste safety-dump safety-dump-retry
|
|
|
|
step "L3 mealie — the edge that was never walked because its drill pin had already moved"
|
|
timeout 2100 python3 run_edge.py mealie ghcr.io/mealie-recipes/mealie:v3.20.1 \
|
|
ghcr.io/mealie-recipes/mealie:v3.27.0 --sub mealie --class db-postgres
|
|
|
|
echo; echo "$(date +%H:%M:%S) leftovers done"
|