wiki audit 2026-10-04: CT450 v0.21.5 update incident, mnemosyne vector-recall FTS-only repair + coverage refresh, managed runtimes 10->3, doctor vec0 caveat
This commit is contained in:
@@ -3,7 +3,7 @@ title: Provider Health Check
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
updated: 2026-10-04
|
||||
verified_on: 2026-07-22
|
||||
last_tested: 2026-07-22
|
||||
confidence: high
|
||||
@@ -84,7 +84,7 @@ Look for repeated failures on Telegram IMAP, Telegram API, Slack Socket Mode, or
|
||||
- Gateway journal shows no red alarm pattern.
|
||||
|
||||
## Current install references
|
||||
- Hermes: v0.19.0, git install: `/home/hermes/.hermes/hermes-agent`
|
||||
- Hermes: v0.21.5+6169.gab86a20 (2026.9.24), git install: `/home/hermes/.hermes/hermes-agent`
|
||||
- LiteLLM base URL: `http://litellm:4000/v1`
|
||||
- OmniRoute base URL: `http://omniroute:20128/v1`
|
||||
- OmniRoute direct IP: `100.88.81.19:20128`
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Update Hermes safely
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
updated: 2026-10-04
|
||||
verified_on: 2026-07-22
|
||||
last_tested: 2026-07-22
|
||||
confidence: high
|
||||
@@ -93,10 +93,30 @@ hermes dashboard restart
|
||||
- If update warns about config migration, revert the backup and re-run manually
|
||||
|
||||
## Notes
|
||||
- Hermes version on this install: v0.19.0 (2026.7.20)
|
||||
- Hermes version on this install: v0.21.5+6169.gab86a20 (2026.9.24); install tree rebuilt 2026-10-03 10:11 AWST
|
||||
- Install directory: `/home/hermes/.hermes/hermes-agent`
|
||||
- Update preserves venv by default unless `--force-venv` is used
|
||||
|
||||
## Second instance — CT450 (`hermesagent`), updated 2026-10-03 (v0.19.0 → v0.21.5)
|
||||
|
||||
CT450 has **no SSH**. Reach it from the PVE host:
|
||||
|
||||
```bash
|
||||
ssh root@100.96.100.82
|
||||
pct exec 450 -- <command> # or: pct enter 450
|
||||
pct exec 450 -- su - hermes -c "/home/hermes/.local/bin/hermes --version"
|
||||
```
|
||||
|
||||
`pct exec 450 -- hermes ...` fails (`Failed to exec "hermes"`): the binary is not on `lxc-attach`'s PATH. Use the absolute path or `su - hermes -c` (the dash gives a login shell, which sets `~/.local/bin`). A `hermes` login shell also prints a `hermes-setup` banner before output.
|
||||
|
||||
**Pre-flight before running the update** (each of these cost one failed run on 2026-10-03):
|
||||
1. `clang` installed — source-compiled Python dependencies will not build without it (`pct exec 450 -- bash -lc "which clang"`).
|
||||
2. No stale `.install.lock` / `.lazy-refresh-incomplete` in the Hermes home.
|
||||
3. `~/.hermes/hermes-agent` owned by `hermes:hermes` (a root-owned tree from an earlier root-run update breaks the in-place build).
|
||||
4. Host Caddy/`keyring` file permissions sane (`0600` keyring blocked a step mid-update).
|
||||
|
||||
**After:** `pct exec 450 -- su - hermes -c "/home/hermes/.local/bin/hermes --version"`, confirm CT460 production is untouched (separate config/skills/cron/memory). Full record: [[incidents/2026-10-03-ct450-hermes-update]].
|
||||
|
||||
## Last tested
|
||||
2026-07-22 on debian 13, git-based Hermes install
|
||||
|
||||
|
||||
Reference in New Issue
Block a user