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
@@ -1,10 +1,10 @@
---
title: "Mnemosyne Capture Pipeline Broken (Aug 18)"
type: incident
status: active
status: superseded
created: 2026-08-18
updated: 2026-08-18
verified_on: 2026-08-18
updated: 2026-10-12
verified_on: 2026-10-12
confidence: high
tags: [memory, mnemosyne, hermes, incident, capture]
sources: [mnemosyne-db, health-monitor, run_agent.py]
@@ -59,6 +59,19 @@ print('Last WM capture:', cur.fetchone()[0]) # Should be recent
"
```
## Current Status (verified 2026-10-12)
**Superseded — capture has been healthy since, and this page is kept for the diagnostic trail.** The 2026-10-12
nightly audit found the full path working: `working_memory` at **786 rows**, +2 on 2026-10-11 (11:19:37 and
11:51:39 UTC = 19:19 / 19:51 AWST, both from that day's interactive session), `episodic_memory` 1,056,
embedding coverage **98.3 % working / 99.6 % episodic**, FTS aligned (`fts_working` 786, `fts_facts` 876).
The three guard conditions diagnosed below were never individually confirmed as the fix — the path resumed
capturing and has captured through every window since.
**Caution for the next alarm:** the health monitor raised a false EXCEPTION on 2026-10-11 00:08 by comparing
naive-UTC `created_at` against AWST `now` ("stalled 10.7 h" — real gap 2.7 h). Do not triage that as a repeat
of this incident; see [[systems/mnemosyne]].
## Prevention
- Never use `hermes config set memory.mnemosyne.<field>` for list/dict/null values
- After any config change, verify YAML types with `yaml.safe_load` + `type()` on each field