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,8 +3,8 @@ title: Restart Hermes
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
last_tested: 2026-10-20
|
||||
confidence: high
|
||||
tags: [runbook, hermes, restart]
|
||||
@@ -85,6 +85,17 @@ pkill -f "hermes-webui/server.py"
|
||||
/home/hermes/.hermes/hermes-agent/venv/bin/python /home/hermes/hermes-webui/server.py
|
||||
```
|
||||
|
||||
> **Steps re-checked live 2026-11-11.** All five user units are **active (running)**:
|
||||
> `hermes-gateway.service`, `hermes-dashboard.service`, `hermes-ui.service`,
|
||||
> `hermes-ui-prod.service`, `hermes-wiki-serve.service`. The gateway runs from the **uv-managed
|
||||
> runtime** (`/home/hermes/.hermes/tools/python-3.14.9+202****1021-linux-x64/bin/python3 … gateway
|
||||
> run`) through the `runpy` bootstrap that carries `_hermes_closure_repair()`; the dashboard is
|
||||
> `hermes dashboard --host 0.0.0.0 --port 9119 --no-open`; the WebUI is still
|
||||
> `/home/hermes/.hermes/hermes-agent/venv/bin/python /home/hermes/hermes-webui/server.py` (port
|
||||
> 8787); `cua-driver serve` is running (PID 4176, cua-driver **0.28.2**); x11vnc is on `:99`/5901.
|
||||
> Note the runtime date-stamp in the interpreter path has advanced (`…14.9+20261021…` vs the
|
||||
> `…14.7+20260901…` recorded on 2026-10-20) — always resolve the path live, never hardcode it.
|
||||
|
||||
## Verification
|
||||
```bash
|
||||
hermes gateway status
|
||||
|
||||
Reference in New Issue
Block a user