stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13) - skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299) - runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated - comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest - incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised - incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused) - 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists) - log.md addendum + index.md date bump; no page deleted, no secrets written
This commit is contained in:
@@ -3,9 +3,9 @@ title: Hermes Gateway Resource Resilience
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-25
|
||||
updated: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
review_after: 2026-11-19
|
||||
verified_on: 2026-10-20
|
||||
verified_on: 2026-11-11
|
||||
version_applies_to: Proxmox CT460
|
||||
confidence: high
|
||||
tags: [hermes, infrastructure, runbook]
|
||||
@@ -96,6 +96,15 @@ consuming most of the container and taking Telegram down with them.
|
||||
> `hermes` user cannot read (permission denied) — its *effective* values are still verifiable via
|
||||
> `systemctl show`, which is what the health-check section below uses.
|
||||
|
||||
> **All effective values re-confirmed live 2026-11-11 via `systemctl show`.**
|
||||
> Gateway (`hermes-gateway.service`, active): `OOMPolicy=continue`, `MemoryLow=536870912`,
|
||||
> `MemoryHigh=infinity`, `MemoryMax=infinity`, `CPUWeight=1000`, `Restart=always`; the drop-in file
|
||||
> still reads `OOMPolicy=continue` / `MemoryLow=512M` / `CPUWeight=1000`. Camofox
|
||||
> (`camofox-browser.service`, active): `OOMPolicy=kill`, `MemoryHigh=2147483648`,
|
||||
> `MemoryMax=3221225472`, `MemorySwapMax=1073741824` — the raised 2G/3G/1G ceilings hold. Web UI
|
||||
> (`hermes-webui.service`, active): `OOMPolicy=kill`, `MemoryHigh=1073741824`,
|
||||
> `MemoryMax=1610612736`, `MemorySwapMax=1073741824`. Unchanged since 2026-10-20.
|
||||
|
||||
## I/O priority limitation
|
||||
|
||||
Do not add `IOWeight` to the gateway drop-in unless Proxmox cgroup delegation
|
||||
|
||||
Reference in New Issue
Block a user