stocktake 2026-10-12: skills-index 346 skills/70 cats; freshness 54 stale/32 fresh/7 no-date; nanobot + home-assistant re-verified live (nanobot web UI back up on :8766, OmniRoute :8900 still closed -> stays degraded; HA HTTP 200 on :8123
This commit is contained in:
+6
-5
@@ -3,8 +3,8 @@ title: Nanobot
|
||||
type: system
|
||||
status: degraded
|
||||
created: 2026-07-22
|
||||
updated: 2026-08-07
|
||||
verified_on: 2026-08-07
|
||||
updated: 2026-10-12
|
||||
verified_on: 2026-10-12
|
||||
confidence: high
|
||||
tags: [system, nanobot, network]
|
||||
sources: [live-probe, omniroute-investigation]
|
||||
@@ -16,9 +16,9 @@ Role in Anthony's setup.
|
||||
## Location
|
||||
- **Verified 2026-07-22:** LXC 333, hostname `clawtest`, Tailscale IP `100.122.189.81`.
|
||||
## Current state
|
||||
- **Status: DOWN (as of 2026-08-07).** Connection refused on port 8900 — the OmniRoute provider connection to nanobot (`58debd59`, prefix `nanobot`) was causing event-loop stalls because every model sync + credential health check retried it. Connection disabled in OmniRoute. Nanobot on CT333 is not responding.
|
||||
- **Prior state:** `nanobot` process listening on port `8766` (verified via `ss -tlnp` on ct333, 2026-07-22).
|
||||
- `whatsapp-bridge.service` (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status unknown as of 2026-08-07.
|
||||
- **Status: DEGRADED (re-verified 2026-10-12).** The Nanobot web UI on CT333 is **UP again**: HTTP `200` on `http://100.122.189.81:8766/` serving the nanobot web UI (verified this audit). However port `8900` — the endpoint the OmniRoute `nanobot` provider connection (`58debd59`, prefix `nanobot`) uses — is still **closed**, so the OmniRoute integration remains disabled. Contrast with 2026-08-07, when connection was refused on 8900 and no service was confirmed listening anywhere.
|
||||
- **Prior state:** `nanobot` process listening on port `8766` (verified via `ss -tlnp` on ct333, 2026-07-22); DOWN 2026-08-07 (connection refused on 8900 — OmniRoute event-loop stalls from model sync + credential health-check retries; provider connection disabled in OmniRoute).
|
||||
- `whatsapp-bridge.service` (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status not re-verified on 2026-10-12 (SSH to CT333 not reachable from CT460: connection timed out on 22/tcp; verification above is TCP/HTTP probing only).
|
||||
- Publicly reachable via the same Cloudflare Tunnel as Hermes: `nanobot.martinwa.org` → `100.122.189.81:8766`, `nano-ssh.martinwa.org` → SSH on the same host. See [[infrastructure/domains-and-tunnels]].
|
||||
|
||||
## Current state as of 2026-07-22 (superseded — see below)
|
||||
@@ -45,6 +45,7 @@ Role in Anthony's setup.
|
||||
## Change history
|
||||
- 2026-07-22: audit corrected "not running" claim after direct verification on ct333.
|
||||
- 2026-08-07: status changed to DEGRADED — nanobot confirmed DOWN (connection refused on 8900). OmniRoute provider connection disabled. CT333 service status unknown.
|
||||
- 2026-10-12: web UI confirmed back up (HTTP 200 on `100.122.189.81:8766`, tailnet IP `100.122.189.81` = tailscale node `clawtest`). Status stays DEGRADED because the OmniRoute port 8900 endpoint is still closed. `whatsapp-bridge.service` not re-verified (SSH to CT333 unreachable from CT460).
|
||||
## Relevant runbooks
|
||||
- [[runbooks/restart-hermes]]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user