6.6 KiB
6.6 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Nanobot | system | degraded | 2026-07-22 | 2026-11-04 | 2026-11-04 | high |
|
|
Nanobot
Purpose
Role in Anthony's setup.
Location
- Verified 2026-07-22: LXC 333, hostname
clawtest, Tailscale IP100.122.189.81.
Current state
- Status: DEGRADED (re-verified 2026-10-12). The Nanobot web UI on CT333 is UP again: HTTP
200onhttp://100.122.189.81:8766/serving the nanobot web UI (verified this audit). However port8900— the endpoint the OmniRoutenanobotprovider connection (58debd59, prefixnanobot) 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:
nanobotprocess listening on port8766(verified viass -tlnpon 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— "WhatsApp Bridge for Nanobot" — also runs on ct333. ⚠ Corrected 2026-11-04: this unit is NOT active — it is in a crash-restart loop. Livesystemctl status whatsapp-bridge.serviceon CT333 showsActive: activating (auto-restart) (Result: exit-code)withNRestarts=75514. TheExecStartis/bin/bash -c cd /home/nano/nanobot/bridge && BRIDGE_TOKEN=$(cat /home/nano/.nanobot/whatsapp-auth/bridge-token) exec node dist/index.js, and it exitsstatus=200/CHDIR— the working directory/home/nano/nanobot/bridgedoes not exist on CT333 (nor does/home/nano/nanobot; only/home/nano/.nanobot/whatsapp-auth/bridge-tokenis present). The unit isenabled, so systemd keeps restarting it every few seconds, burning a restart every ~3 s. The old "systemd, active" claim was wrong and had been carried unverified since 2026-10-12. Verified 2026-11-04 from inside the guest viapct exec 333 -- systemctl status whatsapp-bridge.service— CT333 is reachable from the PVE host even though it was not directly SSH-reachable from CT460 on 2026-10-12 (CT460 → CT333 port 22 now answersTCP22_OPEN).- 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)
- No nanobot process running on this host
-
nanobot systemd user service: inactive- Not present in pgrep process list
Correction (this audit, same day): the above was true only for this host (ct460) — Nanobot was never expected to run here. It is actively running, on LXC 333 ("clawtest"), confirmed via direct process/port check. Left the original lines struck through rather than deleted, per SCHEMA rule 9 (mark, don't silently delete).
History
- User-provided: Nanobox on the PVE host at
192.168.178.39 - Correction:
192.168.178.39ispve's own LAN IP (matches the Cloudflare Tunnel'spve.martinwa.orgentry, which proxies to Proxmox's web UI on that address) — this was a conflation, not a second Nanobot instance. The real Nanobot host is ct333 (see Location above). - Verified: Lan/Wi-Fi node at
192.168.178.46running ARM/arm64 firmware;ubntlogin at192.168.1.1does not apply to this node - Verified: DWARF01 identified as a UniFi device; ONT01 status unresolved; DNS provided by
192.168.178.39, not the router - User-provided: Avoid
heroku.com/archiveexcept for CAPI; use official CAPI course downloads instead - Superseded: "Nanobot may have been used previously as Hermes gateway or tunnel front on another host" / "Unknown: whether nanobot should be redeployed" — no longer applicable now that it's confirmed running; the open question is now why it's running alongside Hermes and whether that's intentional (see comparisons/hermes-vs-nanobot).
Connected systems
Known issues
- Overlap/purpose vs. Hermes not documented anywhere — see comparisons/hermes-vs-nanobot for the open question this raises.
whatsapp-bridge.servicerestart loop (open since at least 2026-10-12, confirmed 2026-11-04).NRestarts=75514and climbing; the cause is a missing/home/nano/nanobot/bridgeworking directory. Two ways to clear it, both needing a decision rather than a blind fix: (a) recreate the directory and redeploy the bridge build, or (b)systemctl disable --now whatsapp-bridge.serviceif the bridge is no longer wanted. Until one is chosen, the unit generates a restart every few seconds indefinitely. The bridge's own auth token (/home/nano/.nanobot/whatsapp-auth/bridge-token) is still present, so the deployment is not merely half-removed.- No monitoring covers either fault. The OmniRoute
8900port being closed and the bridge's restart loop both produce no cron failure and no incident row — the job reads green while the integration is down. That is the same class as the backup-task stall in incidents/2026-11-04-vzdump-freeze-ct299-sftpgo-outage: a service that fails quietly is invisible to a green-row fleet.
Change history
- 2026-11-04:
whatsapp-bridge.serviceclaim corrected — it is crash-looping, not active. The unit is inactivating (auto-restart)withNRestarts=75514, failingstatus=200/CHDIRbecause/home/nano/nanobot/bridgedoes not exist. The page had carried "systemd, active" without verification since 2026-10-12 (that audit could not reach CT333 and said so). Status stays DEGRADED for the same reason as before — OmniRoute's port8900is still closed (livess -ltnon CT333 shows no8900listener) — and now also because the WhatsApp bridge is down. The web UI on:8766remains up (HTTP 200). Root cause of the loop is a missing deployment directory, not a service bug — see systems/nanobot open items. - 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 IP100.122.189.81= tailscale nodeclawtest). Status stays DEGRADED because the OmniRoute port 8900 endpoint is still closed.whatsapp-bridge.servicenot re-verified (SSH to CT333 unreachable from CT460).