FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docker_watchdog: skip required containers stopped cleanly or explicitly paused

Browse Source 
Exit code 0 on a required container (docker stop, UI stop) now reads as
intentional — no strike, no restart. Non-zero exits still trigger the
existing strike → restart path.

Adds --pause / --resume management commands and a persistent intentional-
stops state file for maintenance windows where even the exit-code heuristic
isn't enough. Containers auto-cleared from the list when seen running again.
This commit is contained in:
Gmer4Lfe
2026-06-27 19:00:59 -04:00
parent cf180c1179
commit 75f2a4e3fd
4 changed files with 91 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Notes_To-Do.md
-45
View File
@@ -7,14 +7,9 @@ claude
need a script that check file locations. like if a kids movie is in movies. it needs to detect this and update the location in the arrs. so it would tell radarr to move shrek from movies to kids movies and trck the new file
look at a way to better determine when a container was manually shutdown for docker watchdog
we may need to add this to our preflight before lidarr cleanup. check if lidarr need corrected before
removal. since we have a strike list we can save results of previous scan then run this script then
continue. lidarr has been wierd for the last year. maybe we
────────────────────────────────────────────────────────────────
@@ -27,46 +22,6 @@ we may need to add this to our preflight before lidarr cleanup. check if lidarr
. fix fallback strike list timing, maybe 30 seconds. them a t 90 seconds 3 stike triggers. just gotta test buffer. never had the strike system
. verify silent toggle switches back on good notifications
Saved. Here's where we land and what to pick up:
What happened: Lidarr was silently discarding valid files because it selected the wrong MusicBrainz release edition (Brazil CD, Japan Digital, etc.) while your files were tagged for a different one (US CD, Vinyl). The track IDs don't match across editions, so RescanFolders always returned "Importing 0 tracks." Not a file problem — a database mismatch. The 5GB threshold in lidarr_cleanup.sh was doing exactly what it should.
Fixed this session: 123 albums bulk-corrected (read MUSICBRAINZ_ALBUMID from FLAC tags, switched Lidarr's release selection, RefreshArtist). Full root rescan still running in the background.
Next session — pick up here:
1. Design the daily fixer script (Media/lidarr_release_fixer.sh) — FLAC + MP3 (ID3 TXXX) tag reading, same bulk-fix logic, runs from daily orchestrator. Strike system in lidarr_cleanup.sh already provides the protection window.
2. 42 albums where file MBID isn't in Lidarr at all (unofficial/re-tagged) — manual import or ignore.
3. 217 MP3 albums — need ID3 TXXX frame reader added to the fixer.
4. Check the full root rescan completed and see if zero-file count dropped further below 927.