From 307d25b1742470d350e7b25e1db0b19316d65884 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Wed, 21 Oct 2026 23:59:18 +0200 Subject: [PATCH] STATUS: the morning list after the night run (controller, agent, hub, Tester 2's install, the publishes); D22 and D26 out of the decide table (decided), D27 in (host swap on a no-swap host, R-1207) --- STATUS.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/STATUS.md b/STATUS.md index a45c716d..066e89ad 100644 --- a/STATUS.md +++ b/STATUS.md @@ -1,21 +1,21 @@ # STATUS — what works, what's broken, what's next -**Ready for the first real tester (Tester 2)? No — one step left:** release the agent with the swap fix (decide D26); the 8 GB box can still freeze under big uploads until then. Tester 2 (a laptop) is off; nothing was sent to it. +**Ready for the first real tester (Tester 2)? No — three morning yeses left:** release the controller (the restore put-back, the first-hour words), release and vouch the agent (the swap fix — the night soak says yes or no), deploy the hub. Tester 2 is off; nothing was sent to it. -**Updated 2026-10-21 (evening).** A rebuilt box now gets the household's off-site backups back (hub 0.163.0, proven live: 3 031 files byte-identical), and shared folders, imported apps and away drives keep their copies and locks (controller 0.337.0, the floor). The 8 GB freeze is explained — the guest's swap was capped at 512 MB — and the agent fix is ready but not released. Report: `REPORT-fixes-2026-10-21.md`. +**Updated 2026-10-22 (morning, after the night run).** A failed or cut restore now puts the household's data back and starts the app (proven on the scratch box); the first-hour texts are clearer; a host with too little swap is reported. All built and tested, nothing released. ## What works - A box installs from nothing with the public installer, links to the hub, and moves to the floor by itself (map A1, A3, A4). - 65 catalog apps install, update one tested step at a time, and a failed update undoes itself (map B1, B3, B4, B6). - Backups: database dumps, a second-drive copy, an off-site copy and whole-box copies; restore tests run by themselves (map C1–C4, A17, A18). -- A restore brings an app back with its data and its database password; a failed off-site restore puts the app back as it was (map C5, D6). +- A restore brings an app back with its data and its database password; a failed or cut restore puts the app back as it was — off-site live, local on the test image (map C5, D6, D16). - After a power cut the box starts by itself, cleans up a half-written backup, and Immich repairs broken photos (map C10, F12). - A second drive is offered as the backup target; media apps see every drive; a one-disk box gets its own data area (map D1, D13, D15). - The three test boxes answer only over https; the hub's key opens nothing on a box; password guesses are counted (map E12, E13, E17). - The hub mails alarms and recoveries, and keeps one whole-box copy per week on ep0; CC uses its own limited token, not your password (map F1, F11, G15). ## What is broken -- **P1:** the 8 GB box can freeze for minutes under big uploads until the agent with the swap fix is released (R-1192; cause measured, fix proven by hand for 2 hours). +- **P1:** the 8 GB box can freeze for minutes under big uploads until the agent with the swap fix is released (R-1192; the night soak result is in the morning list). - **P1:** about 12 homelab logins still use a password that was public, and the public Gitea repo is not decided (R-925, yours). - Two root-level weaknesses wait on your decisions D3 and D4 (R-985, R-982). - Tester 2 is off since 2026-10-04: old emergency password, no off-site check, no bootstrap (R-1139, R-1104, R-862). @@ -24,7 +24,6 @@ ## What we work on - Dated checks, run by CC. 2026-10-21 done: the hub's own off-site check found nothing wrong (R-895); downloads stay out of the second-drive copy (closed). 2026-10-23: no app stop when the host is busy (R-1173). 2026-10-26: each hub daily job ran once on the clock-change day (R-1183). 2026-10-27: the weekly clean-up window (R-435; the logs of the last one were lost to restarts). -- A gate keeps this page short and true: it warns now and refuses from 2026-10-27 (R-1174). CC. ## Waiting on you — decide @@ -32,8 +31,7 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te | # | Row | Question | Pick (why) | The other option costs | If you do nothing | Blocked | |---|---|---|---|---|---|---| -| D26 | R-1192 | Release agent 0.162.0 with the swap fix (every guest may swap as much as its RAM), and vouch it? | **Yes, tomorrow morning** (measured: the freeze ended within a minute of the change; 2 hours of the same uploads stayed answering) | Wait: a household's 8 GB box can freeze for minutes, up to an hour, under its first uploads | Tester 2 stays „not ready"; the controller already warns honestly | Tester 2 | -| D22 | R-1177 | A LOCAL restore that fails destroys the live data and keeps no copy. Give it the off-site restore's „put back exactly" (your D20)? | **Yes** (proven live today: a failed restore left the app dead and the newest data gone) | No: a failed local restore can lose the household's newest data | the main restore button can lose data when a backup copy is damaged | — | +| D27 | R-1207 | A host with no swap gets nothing from the swap fix, and the agent never adds swap. Add host swap automatically (BYO too), or refuse an 8 GB host without swap at install? | **Report only for now** (our installer gives 7.75 GB; the alarm and the install-page sentence now tell you) — decide after the first BYO box | Add it: the agent changes a disk its owner set up; refuse: a BYO household cannot start | a no-swap host can still freeze; you get the alarm | — | | D21 | R-49 | Immich's off-site copy: leave out only the AI model files now (B), or also the raw database folder and Immich's own backups (A)? | **B now** (−62 %, no new risk); A's other parts after their proof | A: −92 %, but it needs a restore path we have never run | every Immich box sends about 12 times its real data off-site each night | — | | D9 | R-1062 | Split the N100's USB drive in two, for multi-drive tests? | **No — keep one drive** (the lived-in box keeps its nightly whole-box backup) | Split: the box loses its local whole-box backup, or you buy a second drive first | it stays one drive; multi-drive tests stay on Tester 1 | — | | D8 | R-206 | Install DooPlex's Docker settings from git (Docker restarts once), with a weekly build-cache prune? | **Yes, in a quiet window** (a rebuilt DooPlex then keeps the settings) | No: the live settings stay hand-made, and a rebuild loses them | git and the host can drift apart | — | @@ -54,10 +52,12 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te 6. BIOS: on the N100, read „After Power Loss"; on the HP, set „Bypass F1 Prompt on Configuration Changes" to Enable. Since 2026-10-14. 7. Pin the first Facebook post (R-917), and look at the new cover in the Facebook phone app (R-919). Since 2026-10-12. -**Morning list, 2026-10-21 (fix day).** No decision was taken by CC. -- D26: the agent release with the swap fix. Also new: after a box death with a failed second install, the whole-box backup waits for your „Re-issue PBS credentials" press (R-1205). -- Secrets: keep or remove the `REHEARSAL_2026_10_20_*` and `FIXES_2026_10_21_*` names in sec (the bind, pairing and setup codes are spent; the root password belongs to a deleted box). - +**Morning list, 2026-10-22.** CC decided one thing (you may reverse it): a box tells the hub the notification list its page shows, even if never saved (R-1199; the rehearsal household got 1 alarm of 9). +1. Release controller 0.338.0 (restore put-back incl. power cut, first-hour words, swap sentence)? On the scratch box a damaged backup and a killed controller both kept the newest data and the app running (R-1177, R-1195, R-1178, R-1180). +2. Release and vouch agent 0.162.0 (swap = RAM, host-swap check, no false door alarm — R-1192, R-1194)? The soak result is in the night report. +3. Deploy hub 0.164.0 (host-swap alarm, bind-page words)? +4. Tester 2's laptop: our installer or its own Proxmox? (Does it have host swap?) +5. A publish: the website download button (patch ready), and with the next ISO the boot text and the cleared screen (R-1210). Secrets: keep or remove the `REHEARSAL_2026_10_20_*`, `FIXES_2026_10_21_*`, `NIGHT_2026_10_21_*` names in sec. **The rest** - Pull the failed disk Z6A07P2G out of DooPlex (R-934); it is still in. If not: its alarms return on 11 November. Since 2026-10-12. - Rotate the reused homelab logins and decide the Gitea repo's visibility (R-925, P1). Since 2026-10-09.