stocktake(2026-10-11): skills-index 346 skills/70 cats; freshness 62 stale/24 fresh/7 no-date; 5 live-drift corrections
Drift found and corrected against live sources (not guessed): - OmniRoute: CT600 omniroute is RUNNING and serving :20128 (combo API live); CT601 omni is STOPPED with onboot=0 (peer offline 54d). Wiki had these inverted. Hermes custom:omni resolves to omniroute -> CT600, not CT601. - Third OmniRoute node discovered: omniroute-1 at 100.78.63.20:20128, live (401), registered as custom provider omni-101 (5384 models, default smart-route, carries skills_hub/free-stack). Not in pct list; identity unconfirmed. - Ignis: TWO live instances. CT460 ignis (:8080, vault wiki/agent-estate-wiki) and CT200 ignis-ignis-1 (image ignis-server:latest, host 8092, vault /opt/ignis/vaults). Both return HTTP 200. Page now distinguishes them. - Tailscale: /agent-estate targets bare 127.0.0.1:8769 (was .../8769/agent-estate-role-dashboard.html); undocumented tailnet-only :9443 -> 127.0.0.1:5173 added; CT201 routes corrected (8085 targets + /steel 5173 + /steel-api 3000, replacing the wrong :8443 -> :8082 row). - Proxmox: rebuilt from live pct list + qm list. Added CT475 agentzero and VM110 omarchy (both previously missing); 282 ubuntu-server-xfce corrected to stopped; dead rows removed. VM403 open-claw and VM401 hermes-old absent from qm list - flagged unconfirmed, not deleted. - Nanobot: gateway nanobot-gateway (PID 2259048) alive on 8765/8766. It is NOT systemd nanobot.service/gateway.service (both return inactive - wrong unit names). Port 8900 no longer listening; "Serve API" claim flagged unverified. - Docker: old "runtime not available" was a CT460 socket artifact (root:docker srw-rw----, hermes not in group docker, no passwordless sudo in cron). Documented CT200 (~50 containers), CT333 (9 containers), CT460 via sudo. - Mattermost CT255 confirmed stopped; matches Tailscale peer offline 21d. Flagged, not investigated (no root cause): - mycompose-db-1 on CT200 is in Restarting (1) - crash-looping. 62 pages remain >21d stale and were NOT rewritten this pass (concepts, decisions, comparisons, most runbooks) - not probed against a live source, so reported not faked. Quartz rebuild step still inert (no quartz.config.ts) - public/ not refreshed. Artifacts: systems/skills-index.md regenerated, raw/stocktake/freshness-20261011.txt.
This commit is contained in:
@@ -14,6 +14,21 @@ sources: [live-config, live-cron-list, live-hermes-version]
|
||||
# Current State
|
||||
Updated: 2026-10-11
|
||||
|
||||
## Recent Changes (2026-10-11, 03:00 stocktake; live probes 03:00-03:30 AWST)
|
||||
|
||||
- **OmniRoute CT600/CT601 roles are INVERTED.** CT600 `omniroute` (100.88.81.19) is **running** and serving `:20128` (combo API returns live combos); CT601 `omni` (100.93.204.4) is **stopped** with `onboot=0` (Tailscale peer offline 54d). Hermes resolves `custom:omni` → `omniroute:20128` → **CT600**. → [[systems/omniroute]]
|
||||
- **A third OmniRoute node exists:** `omniroute-1` at `100.78.63.20:20128`, live (401 = auth-required), registered in Hermes config as provider `omni-101` (5384 models, default `smart-route`). It carries `skills_hub` (model `free-stack`) — the same provider family implicated in the 2026-10-09 timeout storm. Not present in `pct list`; identity unconfirmed. → [[systems/omniroute]]
|
||||
- **Two Ignis instances exist, on different hosts.** CT460 `ignis` (port 8080, vault `/home/hermes/wiki/agent-estate-wiki`, serving 200) and CT200 `ignis-ignis-1` (image `ignis-server:latest`, host port 8092, vault `/opt/ignis/vaults`, serving 200). Both healthy; they are separate deployments. → [[systems/ignis]]
|
||||
- **Tailscale route drift fixed:** `/agent-estate` targets bare `http://127.0.0.1:8769` (page had `.../agent-estate-role-dashboard.html`); a tailnet-only `:9443` → `127.0.0.1:5173` Serve was undocumented. CT201's live routes are 8085-based plus `/steel` (5173) and `/steel-api` (3000) — the old `:8443` → `localhost:8082` Homepage row is wrong. → [[infrastructure/tailscale]]
|
||||
- **Proxmox inventory rebuilt** from `pct list` + `qm list`: **CT475 `agentzero` and VM110 `omarchy` were missing entirely**; 282 `ubuntu-server-xfce` corrected to stopped; dead rows removed (310, 500, 104, 106, 101). **VM403 `open-claw` and VM401 `hermes-old` are absent from `qm list`** — flagged unconfirmed, not deleted. → [[infrastructure/proxmox]]
|
||||
- **Nanobot verified on CT333:** `nanobot-gateway` (PID 2259048) alive on 8765/8766. It is **not** a systemd `nanobot.service`/`gateway.service` (both probes return `inactive` — wrong unit names); it runs as the `nanobot` user service plus the gateway process. Port **8900 is no longer listening** — previous "Serve API" claim flagged unverified. → [[agents/nanobot]]
|
||||
- **Docker services page corrected:** the old "Docker runtime not available" line was a CT460 socket artifact (`/var/run/docker.sock` is `root:docker srw-rw----`; `hermes` user not in group `docker`; no passwordless sudo in cron). Real fleet: CT200 holds ~50 containers, CT333 holds 9. → [[infrastructure/docker-services]]
|
||||
- **Mattermost CT255 confirmed stopped**, consistent with its Tailscale peer being offline 21d. Root cause of the unreachable endpoint still undetermined.
|
||||
- **⚠ `mycompose-db-1` on CT200 is in `Restarting (1)`** — crash-looping. Flagged; root cause NOT investigated this pass.
|
||||
- Stocktake artifacts: skills-index regenerated (**346 skills / 70 categories**), `raw/stocktake/freshness-20261011.txt` = **62 stale / 24 fresh / 7 no-date of 93 pages**.
|
||||
- **Quartz rebuild still inert** (no `quartz.config.ts`) — `public/` was not refreshed. Carried open item; unchanged from prior days.
|
||||
- 62 pages remain >21d stale and were **not** corrected this pass: they were not probed against a live source, so they stay flagged rather than rewritten.
|
||||
|
||||
## Recent Changes (2026-10-10 -> 10-11, nightly audit of the 2026-10-09 -> 2026-10-10 window; probes 2026-10-11 00:14-00:20 AWST)
|
||||
|
||||
_The manual 2026-10-10 stocktake entry follows beneath this one._
|
||||
|
||||
Reference in New Issue
Block a user