audit(2026-10-12): cron fleet clean 2nd day (10-11 171/0, 10-10 finalised 175/0); UTC-vs-AWST false 'capture stalled' alarm corrected; proxmox storage table + host mounts; queries/retained-research-answers stub filled (VNC); capture-pipeline incident -> superseded; index stale labels fixed

This commit is contained in:
Tony0410
2026-10-12 00:14:11 +08:00
parent d981e30128
commit 6fc109e546
8 changed files with 205 additions and 29 deletions
+33
View File
@@ -472,3 +472,36 @@ No secrets written; job/incident IDs, paths and tailnet addresses only.
- **Flagged for follow-up, root cause not investigated:** `mycompose-db-1` on CT200 is in `Restarting (1)` — crash-looping.
- Mattermost CT255 confirmed stopped, matching its Tailscale peer offline 21d.
- Left as stale-without-fix: 62 pages still older than 21 days (concepts, decisions, comparisons, most runbooks) — these were not probed against a live source this pass, so they were reported, not rewritten.
## [2026-10-12] wiki audit | window 2026-10-11 -> 2026-10-12 (ran 2026-10-11 23:59 -> 2026-10-12 00:2x AWST)
**Cron.** 29 jobs, 26 enabled / 3 disabled (`jobs.json` 2026-10-12T00:10). Day tally: 10-07 `177/1`,
10-08 `178/2`, 10-09 `163/15`, 10-10 **`175 completed / 0 failed`** (finalised), 10-11 **`171 completed /
0 failed`** + 1 `running` — **two consecutive clean days**. Non-clean `last_status` steady at 5;
**0 incidents opened, 0 closed — 5 unresolved** (3 `alerted`, 2 `detected`).
**Corrected a false alarm instead of logging a fault.** The 2026-10-11 00:08 Mnemosyne Health Monitor
EXCEPTION ("capture stalled 10.7 h") was a **naive-UTC vs AWST comparison error** — real gap 2.7 h, the row it
cited landed inside the session that wrote it. Recorded in [[systems/mnemosyne]] and
[[systems/scheduled-tasks]] so the next run of that monitor is not triaged as a capture outage. Live counts
refreshed: 786 WM / 1,056 EP, coverage 98.3 % / 99.6 %.
**New content.** [[queries/retained-research-answers]] was a 2026-07-22 stub and is now a real page — the
2026-10-11 VNC-client research (server-side encoder is the bottleneck; TigerVNC native viewer for standard RFB;
`-CompressLevel` 2 is client-side; RealVNC's "4.7×" is self-referential) with its sources. Proxmox storage
was undocumented; the live datastore table plus host mount points are now in [[infrastructure/proxmox]]
(`/mnt/ssd0` 93 % / ~63 GiB free is the pressure point).
**Stale labels fixed.** [[incidents/2026-08-18-mnemosyne-capture-pipeline]] carried `status: active` from
August despite capture being verifiably healthy — now `superseded`, with the live evidence and a caution about
the UTC comparison. Index's "8 incidents still open" from the 2026-10-09 storm trimmed to the 2 genuinely open,
and the skills-index blurb no longer claims no regeneration since 2026-10-07.
**Verified, not changed.** The `blocked-page-recovery` lesson that session reported patching
(`recovered: false` = archive routes failed, not task failed; API-first rung) is present in the live skill.
**Pages touched:** `systems/scheduled-tasks.md`, `systems/mnemosyne.md`, `infrastructure/proxmox.md`,
`queries/retained-research-answers.md`, `incidents/2026-08-18-mnemosyne-capture-pipeline.md`,
`current-state.md`, `index.md`, `log.md`.
No secrets written; job/incident IDs, paths and tailnet addresses only.