audit 2026-11-08 (window 11-07): cron claim loss in gateway restart drain (2 runs orphaned, 2 incident rows unalerted); Hermes 0.22.5->0.23.0 (snapshot skipped), camofox plugin 1.1.0, conduit 0.134.4, hq-push 0.9.42, opencode-go key expired; skills 302->299 (4 archived); freshness 0/126/3 of 129
This commit is contained in:
+26
-3
@@ -3,9 +3,9 @@ title: Conduit
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-10-24
|
||||
updated: 2026-11-01
|
||||
verified_on: 2026-11-01
|
||||
review_after: 2026-11-08
|
||||
updated: 2026-11-08
|
||||
verified_on: 2026-11-08
|
||||
review_after: 2026-12-08
|
||||
confidence: high
|
||||
tags: [conduit, plugin, phone, iphone, push, voice, memory, tool-calling, session-ttl]
|
||||
sources: [live-probe, plugin-tree, live-sqlite-conduit, live-sqlite-cron, live-log, session-20261024_125329, session-20260908_031541_49c051]
|
||||
@@ -207,6 +207,29 @@ mode never applies** despite a passing connection test.
|
||||
**4,384 `buckets`** / **504 `windows`**; ≈**8 MB/day**, no retention policy.
|
||||
- **Not re-measured:** per-kind event split, health-table freshness, device pairing state.
|
||||
|
||||
## 2026-11-08 00:4x AWST — self-updated again to 0.134.4, and its last step failed
|
||||
|
||||
The plugin updated itself in-window and its own ledger records the final step as **failed**:
|
||||
|
||||
~/.hermes/conduit-self-update.json
|
||||
{"id": "916d72daeb644b06b5ae1359ddfdd992", "step": "failed", "from_version": "0.122.2",
|
||||
"version": "0.134.4", "failed_step": "restarting_gateway",
|
||||
"detail": "The plugin is updated, but the gateway didn't restart. Run hermes gateway status on the host.",
|
||||
"started_at": 1793996875.92, "finished_at": 1793997152.39, "pid": 176771, "boot_id": "f292ee44712be8b3"}
|
||||
|
||||
- Window: **2026-11-07 04:27:55 → 04:32:32 AWST** (276 s). `from_version` **0.122.2** (the version this page
|
||||
recorded on 2026-11-01) → **0.134.4**; `hermes plugins list` and the plugin tree agree.
|
||||
- `failed_step: restarting_gateway` is literal: the gateway was **not** restarted at 04:32 — `pid 176771`
|
||||
was still the live gateway at 04:59 and only restarted at **05:01:00** (systemd), then again at 05:43 as
|
||||
part of the Hermes 0.22.5 → 0.23.0 update ([[systems/hermes-agent]]).
|
||||
- **Consequence, and the reason this is recorded here:** a restart was requested at ~04:29:52 and held for
|
||||
the full 1800 s *after-turn* window, then drained — which killed two in-flight cron runs
|
||||
([[incidents/2026-11-07-cron-claim-loss-in-gateway-restart-drain]]). *Working hypothesis, not proven:* the
|
||||
requester was this self-update. Either way, **a plugin under `~/.hermes/plugins/` cannot restart a
|
||||
systemd-managed gateway itself**, and it reported failure rather than retrying.
|
||||
- The plugin remained enabled and functional throughout; no user-facing conduit fault was recorded on
|
||||
2026-11-07.
|
||||
|
||||
## Open items
|
||||
- ✅ **Resolved 2026-11-01** — the `plugin_api.py` timeout patch is no longer needed: the tree is clean
|
||||
at `0.122.2` and `MEMORY_TIMEOUT_S` ships upstream in `dashboard/api/memory.py`.
|
||||
|
||||
Reference in New Issue
Block a user