Block a user
Updater never prunes Docker build cache: node-002 disk hit 100% and silently stopped recording for 17 days
Correction to the stated cause: node-002 runs the updater with BUILD=0 (REF=v1), so the 39.5 GB build cache did not come from the updater building on each update. It came from earlier local builds…
drb-update: prune build cache and stale images after every update (#41)
Updater never prunes Docker build cache: node-002 disk hit 100% and silently stopped recording for 17 days
node-002 remediated 2026-10-26 ~05:00 UTC: docker builder prune -af + image prune -af freed the disk from 100% to 55% (43 GB free); restarted edge-node; owner confirms it is recording again.…
drb-update: prune build cache and stale images after every update (#41)
Updater never prunes Docker build cache: node-002 disk hit 100% and silently stopped recording for 17 days
Report decode health in the checkin so the portal can explain "online but not recording"
Data point after Restart OP25 (23:41): node-002 produced a call doc at 23:45 (MTA PD Districts 6/7/11 Dispatch, 14s), so OP25 is decoding and call_start/call_end reach C2 over MQTT, but the call…
Report decode health in the checkin so the portal can explain "online but not recording"
Frontend: fixes from the 10-25 Chrome sweep
Frontend: fixes from the 10-25 Chrome sweep
Live map: stale-state dim greys out popups and legend; node pins nearly invisible on the dark basemap
Expired session renders pages signed-out instead of redirecting to login