Nightly audit 2026-11-03 (window 2026-11-02): new incident — Job Radar Stage 1 iteration-cap recurrence (9h 01m, suppressed, no incident raised); Weekly Review incident resolved (reconciled 01:27 AWST); scheduled-tasks + browser-backend re-verified; index/log updated

This commit is contained in:
Tony0410
2026-11-03 00:22:13 +08:00
parent fda56e53fe
commit ca014efd63
8 changed files with 516 additions and 20 deletions
+15 -2
View File
@@ -3,8 +3,8 @@ title: Browser Backend
type: system
status: active
created: 2026-07-22
updated: 2026-10-29
verified_on: 2026-10-29
updated: 2026-11-03
verified_on: 2026-11-03
confidence: high
tags: [browser, camofox, automation]
sources: [live-probe, config, session-history]
@@ -112,6 +112,19 @@ until the next session starts.
on **CT201** (containers, images, network, project dir, Serve routes) and **CT333** (container + image)
torn down. Camofox is the sole backend.
- **2026-11-02 — the HTTP server wedged at the start of a browser-heavy cron run; a restart cleared it.**
The 07:00 Job Radar Stage 1 (`dca8482e4f76`) found the REST server accepting nothing — requests timing out
with **no lines reaching the service log** — before its first tab was opened. `systemctl --user restart
camofox-browser.service` cleared it and the run went on to work four boards. **Live re-probe
`2026-11-03 00:16:14 AWST`:** unit `active`, `MainPID 953299`, `ActiveEnterTimestamp Mon 2026-11-02
18:11:04`, `MemoryCurrent 37.5 MB`; `/health` → **200**
`{"ok":true,"engine":"camoufox","browserConnected":false,"browserRunning":false,"activeTabs":0,"activeSessions":0,"consecutiveFailures":0}`;
`/tabs` → `{"running":true,"tabs":[]}`. Idle-clean and far inside the containment drop-in.
⚠ **This is a different fault from the 2026-10-12 ceiling:** that one was memory exhaustion under many
open tabs (`2.5G`, swap fully consumed); this one was a **hung HTTP server at 31 MB RSS**, so the
containment limits are not the control that applies. A health probe inside browser-heavy scripts should
therefore test **responsiveness**, not just `/health` status code.
## Correction (2026-10-29) — Steel is out of the stack, not just disabled
Verified against live state at **2026-10-29**. The earlier 00:3x probe said only "not reachable"; the truth is