From dfc237e6d447d3bd6ab7709508c967c3b52af16c Mon Sep 17 00:00:00 2001 From: Mike Swanson Date: Mon, 6 Jul 2026 11:02:12 -0700 Subject: [PATCH] sync: auto-sync from GURU-5070 at 2026-07-06 11:01:42 Author: Mike Swanson Machine: GURU-5070 Timestamp: 2026-07-06 11:01:42 --- .../2026-07/2026-07-05-mike-dos-spec-fix-telemetry-udm.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/clients/dataforth/session-logs/2026-07/2026-07-05-mike-dos-spec-fix-telemetry-udm.md b/clients/dataforth/session-logs/2026-07/2026-07-05-mike-dos-spec-fix-telemetry-udm.md index c40bc523..84c43934 100644 --- a/clients/dataforth/session-logs/2026-07/2026-07-05-mike-dos-spec-fix-telemetry-udm.md +++ b/clients/dataforth/session-logs/2026-07/2026-07-05-mike-dos-spec-fix-telemetry-udm.md @@ -88,3 +88,10 @@ No new credentials created or discovered. Used (read-only) from vault: - Batch source of truth: `projects/dataforth-dos/batch-files/`. Tier-A design: `projects/dataforth-dos/docs/TIER-A-STATION-TELEMETRY.md`. - Boot flow: `AUTOEXEC → STARTNET → NWTOC (download) → CTONW (upload) → menux`. NWTOC pulls `COMMON\ProdSW\*.BAT` → `C:\BAT` each boot (self-update path; broken v5.0 `/Y` cannot bootstrap v5.1). - SHAs above are file content hashes (sha256) used for deploy verification, not git commits. + +## Update — UDM incident resolved + SYSTAT wired + +- **UDM incident CLOSED.** VPN restored the `192.168.0.x` route; direct SSH confirmed: `unifi-protect`/`access`/`talk` + `freeswitch` packages **and services all gone**, memory recovered (available **998 MB → 1371 MB**, used down ~380 MB), `unifi.service` healthy (RSS ~365 MB, was ~450 MB), `ace` DB **299 clients**. UDM **uptime 16 days — it never rebooted**; the earlier "unreachable" stretch was a **routing gap**, not the UDM going down. Root cause (memory starvation from three unneeded apps on a 4 GB UDM) eliminated → recurrence unlikely. +- **Correction / topology:** D2TESTNAS (RMM agent `ix.azcomputerguru.com`) is on the **`172.16.x` segment** (default gw `172.16.0.1`) and **cannot reach `192.168.0.x`** (no ARP for the UDM, can't ping AD2 either) — so it was the wrong vantage point; its "UDM down" reads meant "D2TESTNAS can't route there." The on-segment vantage point is **AD2 (`192.168.0.6`)**, or a direct VPN/Tailscale route. Twice this session, verifying beat assuming (the boot-hang, and this). +- **SYSTAT wired:** `CTONW v5.3` promoted live via AD2's **new** RMM id `4b9fe588` (old `cfa93bb6` stale after re-enroll). `CTONW.BAT` = v5.3 (2121 B); paused SYSTAT status page now runs before menux fleet-wide. Rollback `CTONW52.BAT` (v5.2). +- **Still open:** #32489 John reply (drafted, held) + billing (needs minutes + labor type) + ticket status.