Files
felhom.eu/documentation/audits/release-2026-10-09/proofs/D3/d3.txt
T

43 lines
3.8 KiB
Plaintext

== D3 on tester-1 2026-10-09T06:04:10Z: docker stop filebrowser (a protected container) in guest 9201
filebrowser
2026/10/09 08:08:32 [INFO] Event from tester-1: health_critical (error) — Rendszer állapot kritikus (volt: ok)
2026/10/09 08:08:33 [INFO] Operator email sent for tester-1/health_critical
household mail: none — tester-1 has no customer_notifications row (no household address set), so the dispatcher returns before sending (dispatcher.go, prefs == nil). Read from a hub DB copy with its WAL.
== docker start filebrowser 2026-10-09T06:09:28Z
filebrowser
== 2026-10-09T06:09:57Z Tester 1 dashboard POST /settings/notifications: household address tester1@felhom.eu (our catch-all), the same 13 default events (was: no address)
-> 200
== run 2 2026-10-09T06:13:48Z: docker stop filebrowser again (household address now set)
filebrowser
2026/10/09 08:18:32 [INFO] Event from tester-1: health_critical (error) — Rendszer állapot kritikus (volt: ok)
2026/10/09 08:18:32 [INFO] Operator email suppressed for tester-1/health_critical — cooldown (key=tester-1:health_critical)
2026/10/09 08:18:33 [INFO] Customer email sent to (catch-all) for tester-1/health_critical
== docker start filebrowser 2026-10-09T06:18:44Z
== the household mail, read from the catch-all (Gmail, a different channel from the hub log), 2026-10-09T06:18:33Z to tester1@felhom.eu
Subject: [Felhom] Hiba: A rendszer állapota kritikus!
Kedves Ügyfél! / A Felhom rendszered a következő értesítést küldte: / A rendszer állapota kritikus! / Részletek: - Szerver: tester-1
- Időpont: 2026-10-09 08:18 - Szint: Hiba - Típus: health_critical - Üzenet: Rendszer állapot kritikus (volt: ok)
A részleteket a vezérlőpultodon látod. / Ha kérdésed van, vedd fel a kapcsolatot az üzemeltetővel.
CHECK: no "{" in the body (yes); the dashboard line is there (yes).
== the operator mail (run 1), 2026-10-09T06:08:33Z to admin@felhom.eu: "[Felhom] 🔴 tester-1: health_critical" — it still carries
Details: {"previous_status":"ok",...} (the note stays on the operator's side). The run-2 operator mail was held by its 6 h cooldown.
== 2026-10-09T06:19:23Z household address cleared (empty address + no events: the dashboard's guard refuses an empty address with events ticked): 200
2026/10/09 08:19:23 [INFO] Notification preferences updated for tester-1: email=tester1@felhom.eu, events=[]
hub row after the clear: address kept by the hub's empty-email no-clobber guard (handler.go, v0.71.0, by design), events=[] -> no household mail is sent (isEventEnabled). Behaviour as before the proof: no household mail.
== D3 dashboard half on scratch 9202 2026-10-09T06:19:59Z
language -> en: 302
stopped: filebrowser
06:30:11 dashboard (English): positive 'A protected system service is not running: filebrowser' -> 0; negative (Hungarian) 'rendszerszolgaltatas'/'nem fut' ASCII fragment -> 0; html lang -> lang="en"
note: on 9202 only traefik is a protected container (no tunnel, no samba), so stopping filebrowser raised no issue there; the controller's base-stack self-heal started it again at 06:24:24. The household-language check reads 9202's EXISTING health banners instead.
06:31:01 English dashboard (lang=en), the health banners:
- Storage not reachable: /mnt/felhom-drives/scratch_hdd/userdata/grimmory System monitor →
- Storage not reachable: /mnt/felhom-drives/scratch_hdd/userdata/metube System monitor →
- The hub connection is off — central monitoring is not running System monitor →
language -> hu (as found): 302
control, Hungarian dashboard, the same banners:
- Adattároló nem elérhető: /mnt/felhom-drives/scratch_hdd/userdata/grimmory Rendszermonitor →
- Adattároló nem elérhető: /mnt/felhom-drives/scratch_hdd/userdata/metube Rendszermonitor →
- Hub kapcsolat kikapcsolva — a központi monitoring nem aktív Rendszermonitor →