4.5 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CT450 Hermes Update to v0.21.5 | incident | resolved | 2026-10-04 | 2026-11-18 | 2026-11-18 | high |
|
|
CT450 Hermes Update to v0.21.5
Summary
The Chaos instance (LXC CT450, hermesagent) was updated v0.19.0 → v0.21.5 on 2026-10-03 — its first update since July. CT460 (production) was rebuilt the same morning, so both instances now carry the same semver token from separate builds.
Result (live-verified 2026-10-04)
| CT460 (production) | CT450 (chaos) | |
|---|---|---|
| Version | v0.21.5+6169.gab86a20 (2026.9.24) |
v0.21.5+6170.ga510d6c (2026.9.24) |
| Upstream | ab86a20a |
a510d6c6 — 3 commits behind, hermes update available |
| Python | managed runtime 3.14 (legacy venv/ 3.11.15) |
3.14.7 |
| Install tree mtime | 2026-10-03 10:11 AWST | 2026-10-03 10:22 AWST |
Access
CT450 has no SSH. Reach it through the PVE host:
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"
Two gotchas that cost time:
pct exec 450 -- hermes ...fails withFailed to exec "hermes"— the binary is not onlxc-attach's default PATH. Use the absolute path, orsu - hermes -c(the dash matters: only a login shell puts~/.local/binon PATH).- A
hermeslogin shell prints ahermes-setupbanner ahead of command output; parse with| tail -nrather than expecting clean stdout.
Pre-flight checks (each cost one failed run on 2026-10-03)
- Build toolchain.
clangmust be present before updating — source-compiled Python dependencies will not build without it. Verified present on CT450 (/usr/bin/clang, 2026-10-04). - Stale update locks. A leftover
.install.lock/.lazy-refresh-incompletein the Hermes home makes the updater refuse or silently skip the refresh step. Neither exists on CT450 now. - Install-tree ownership.
~/.hermes/hermes-agentmust stay owned byhermes:hermes(uid 1000); a root-owned tree left by an earlier root-run update fails the in-place build. - Caddy keyring permissions. Host-level Caddy/
keyringfile permissions (0600) blocked a step mid-update — check them before starting, not during.
Verification
hermes --versionon CT450 →Hermes Agent v0.21.5+6170.ga510d6c (2026.9.24) · upstream a510d6c6, Python 3.14.7.- Install tree mtime
2026-10-03 10:22matches the update window. clangpresent; no stale locks present.- CT460 production untouched — separate config, skills, cron and memory state.
Current state (re-verified 2026-10-26)
Both instances have since moved on: CT460 and CT450 now both run v0.22.3 (2026.9.24), local 5b147ab036d6 — the same build. CT450 is 0 commits behind origin/main (the "3 commits behind" note below is superseded), though hermes update --check reports stable v0.22.5 available on both. CT450's default model is now smart-route on custom → http://100.78.63.20:20128. The CT450 Mattermost timeout remains — CT255 is SUPERSEDED 2026-11-18 — CT255 is stopped on pve and its peer has been offline 36 d, so it is an infrastructure condition, not an update regression.running and its peer online; see the 11-18 state above.
Current state (re-verified 2026-11-18)
Both instances have moved on again and are now on different builds: CT460 runs v0.23.0 (local 2bd378ed1b8d), CT450 runs v0.23.1 (local 3b4215785882) — CT450 is one patch ahead and 0 commits behind origin/main. The 10-26 Mattermost condition is superseded: CT255 (mattermost) is running on pve and its tailnet peer is online, so the old "CT255 stopped / peer offline 36 d" note no longer describes reality.
Follow-ups
CT450 reportsSUPERSEDED 2026-10-26 — CT450 is now 0 commits behindUpdate available: 3 commits behind.origin/main(it tracks theNousResearch/hermes-agentmainbranch; there is noorigin/masteron that remote). Re-runhermes updateif the chaos box should track upstream exactly.- CT450's Mattermost connection is failing (
mattermost connect timed out after 30s, retried every 300s) — an infrastructure condition (Mattermost host unreachable), not an update regression. See agents/hermes-chaos.