TODO: how to verify a web-UI update actually restarted the app

The web-UI update restarts via os.execv in the same process, so systemd's
ActiveEnterTimestamp doesn't change. Check for a "[skus] Loaded" startup
line after the release was pushed instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
StyxX65andClaude Opus 5.5 committed 2026-09-28 14:57:12 +02:00
1 parent 5e60d17d60
commit 5e0ce6996b
1 file changed
+3 -1
+3 -1
View File
@@ -63,8 +63,10 @@ git -C /opt/gdprscanner log --oneline -1 # expect the release commit on
cat /opt/gdprscanner/VERSION # expect the released version cat /opt/gdprscanner/VERSION # expect the released version
git -C /opt/gdprscanner status --short # expect no output git -C /opt/gdprscanner status --short # expect no output
git -C /opt/gdprscanner stash list # any entries = local changes the updater set aside git -C /opt/gdprscanner stash list # any entries = local changes the updater set aside
systemctl show gdprscanner -p ActiveEnterTimestamp # must be after the update systemctl show gdprscanner -p ActiveEnterTimestamp # must be after the update (CLI/cron updates only)
journalctl -u gdprscanner --since "<update time>" --no-pager | grep "\[skus\] Loaded" # one line per app start
``` ```
The **web-UI update** (Settings → Software update) restarts via `os.execv` in the same process (same PID), so `ActiveEnterTimestamp` does **not** change — use the `[skus] Loaded …` startup line instead: there must be one after the release commit was pushed. (`[ou-roles] Loaded …` lines are logged per account-list load, not per start.)
Then hard-refresh the browser (Cmd+Shift+R) before scanning. Also confirm `git -C /opt/gdprscanner remote -v` points at `https://git.fejl40.nu/Fejl40.nu/GDPRScanner.git` (the repo moved from GitHub). Then hard-refresh the browser (Cmd+Shift+R) before scanning. Also confirm `git -C /opt/gdprscanner remote -v` points at `https://git.fejl40.nu/Fejl40.nu/GDPRScanner.git` (the repo moved from GitHub).
**If it recurs, collect:** the log from "Starter scanning: …" onward (look for *"Ingen Microsoft 365-konti valgt"*, *"Sprang N konto(er) over, der kun findes i Google Workspace"*, or no Outlook/OneDrive lines at all); how the scan was started (profile / hand-ticked / scheduled job) and which profile; whether the Elev/Ansat filter or search was active; and the output of the checks above. **If it recurs, collect:** the log from "Starter scanning: …" onward (look for *"Ingen Microsoft 365-konti valgt"*, *"Sprang N konto(er) over, der kun findes i Google Workspace"*, or no Outlook/OneDrive lines at all); how the scan was started (profile / hand-ticked / scheduled job) and which profile; whether the Elev/Ansat filter or search was active; and the output of the checks above.