From 59c76035d384bc11729b0a3cca69bbc2abbcfedc Mon Sep 17 00:00:00 2001 From: Frank Date: Fri, 18 Sep 2026 08:15:14 -0700 Subject: [PATCH] log: frank-medium left down after bench round 04:25, restored and verified --- serverAppConfigs-docs/log.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/serverAppConfigs-docs/log.md b/serverAppConfigs-docs/log.md index bb87930..9bd7bbc 100644 --- a/serverAppConfigs-docs/log.md +++ b/serverAppConfigs-docs/log.md @@ -885,3 +885,23 @@ timestamp: 2026-09-14 - **Deploy verified live:** sightsound pruned (state 0, trashed 20260917), `/docs` 200 on the post-auth listener, all three model cards `up`, bats 329 green, e2e gate 32 passed. + +## 2026-09-18 (morning) — frank-medium found stopped after a bench round + +- **Symptom:** connection refused on `192.168.0.235:7770`. Not network — + the unit itself was `inactive` (enabled, unmasked, `NRestarts=0`). +- **Root cause (from sudo journal):** the AGENTS.md bench protocol was + executed from `PWD=/home/dank` — `stop` + `mask` at 02:47:00, `unmask` + + `start` at 04:21:27, then a final `stop` at 04:25:59 that was never + followed by the protocol's step 3 (unmask/start + health verify). + A bench round ended and left the endpoint down; no crash involved. +- **Restore:** GPU confirmed idle first (both R9700s ~60 MiB, no + `llama-bench`/`llama-server` procs), then `systemctl start + frank-medium`. Health 200 on first probe; `/proc/MainPID/cmdline` + confirms the deployed geometry (`--tensor-split 35,30`, ctx 393216, + 2 slots, batch 6144x512, `draft-mtp`); a real completion returns + verbatim. Fingerprint `b11009-fb27a525d` = the pinned runtime. +- **Lesson:** the restore half of the bench protocol is not optional. + If you bench from an agent session, the session owes the fleet a + `health 200` before it ends. Consider making the bench harness + self-restoring.