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
+12 -3
View File
@@ -3,8 +3,8 @@ title: Current State
type: concept
status: active
created: 2026-07-22
updated: 2026-10-11
verified_on: 2026-10-11
updated: 2026-10-12
verified_on: 2026-10-12
review_after: 2026-10-25
confidence: high
tags: [system]
@@ -12,7 +12,16 @@ sources: [live-config, live-cron-list, live-hermes-version]
---
# Current State
Updated: 2026-10-11
Updated: 2026-10-12
## Recent Changes (2026-10-11 → 2026-10-12, nightly audit; live probes 2026-10-12 00:0x-00:2x AWST)
- **The cron fleet is clean for a second consecutive day: 2026-10-11 ran `171 completed / 0 failed`** (+1 `running` = this audit), after 10-07 `1` / 10-08 `2` / 10-09 `15` failed. 10-10 finalises at **`175 / 0`**. Fleet **29 jobs — 26 enabled / 3 disabled**; non-clean `last_status` steady at **5**; **0 incidents opened, 0 closed — 5 unresolved** (3 `alerted`, 2 `detected`). The two streak-1 jobs (`dca8482e4f76`, `1b23c042e17d`) carry Friday 2026-10-09 timeouts and have not had a scheduled slot since. → [[systems/scheduled-tasks]]
- **The 2026-10-11 00:08 "memory capture stalled" EXCEPTION was a timezone mislabel, not a capture fault.** `working_memory.created_at` is naive UTC; the monitor compared it against AWST `now` and reported a 2.7 h gap as 10.7 h. Capture verified healthy: 786 rows, +2 in the window, coverage 98.3 % working / 99.6 % episodic. → [[systems/mnemosyne]]
- **Proxmox storage documented for the first time:** `/mnt/ssd0` is the pressure point — 808 GiB used, **~63 GiB free (93 % by `df`, 88.1 % by `pvesm`)**; `SSD1` 86.1 %, `fred-qnap` 76.8 %, `iMacHDD` inactive. → [[infrastructure/proxmox]]
- **First retained research answer filed:** fastest VNC clients (asked 2026-10-11) — the server-side encoder is the real bottleneck, TigerVNC native viewer for standard RFB, `-CompressLevel` is a *client* parameter, RealVNC's "4.7×" is self-referential. → [[queries/retained-research-answers]]
- **Only one interactive session in the window** (`talaria-ios`, 19:13 → 19:51, 41 messages); the other 17 were `cron`. The 03:00 stocktake `1a8e90ea2271` completed on schedule (03:00:40 → 03:11:29) and committed `d981e30`.
- **Stale labels corrected:** [[incidents/2026-08-18-mnemosyne-capture-pipeline]] moved from `active` to `superseded` (evidence above); the index's count of open 2026-10-09 storm incidents trimmed to the 2 that are genuinely open.
## Recent Changes (2026-10-11, 03:00 stocktake; live probes 03:00-03:30 AWST)