From 4effb55756e6649ecdb481a6c1e08d2adcba773e Mon Sep 17 00:00:00 2001 From: Gmer4Lfe Date: Mon, 1 Jun 2026 19:50:31 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20fix=20root=20Manual,=20README,=20User?= =?UTF-8?q?=5FScript=5FPlug-in=20=E2=80=94=20boot=20drive=20paths,=2015min?= =?UTF-8?q?=20watchdog,=20scheduler=20setup=20replaces=20User=20Scripts=20?= =?UTF-8?q?section?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Manual.md | 99 ++++++++++++++--------------- README-User_Script_Plug-in.md | 115 ++++++++++++++++++---------------- README.md | 4 +- Tools/Manual-Tools.md | 2 +- 4 files changed, 110 insertions(+), 110 deletions(-) diff --git a/Manual.md b/Manual.md index dc5535f..c4f96c2 100644 --- a/Manual.md +++ b/Manual.md @@ -30,7 +30,7 @@ Install these via **Apps** (Community Applications) on both servers: | Plugin | Why | |--------|-----| | **Tailscale** | Encrypted VPN between servers — all script traffic travels over it | -| **User Scripts** | Schedules the orchestrators (replaces per-script cron entries) | +| **User Scripts** | Required for "At Startup of Array" hook — array_started.sh entry only | --- @@ -89,8 +89,8 @@ hostname ### ── Clone on HOST1 ─────────────────────────────────────────────────────────── ```bash -git clone /mnt/user/appdata/Varaverk -cd /mnt/user/appdata/Varaverk +git clone /boot/config/plugins/varaverk +cd /boot/config/plugins/varaverk ``` --- @@ -98,8 +98,8 @@ cd /mnt/user/appdata/Varaverk ### ── Clone on HOST2 ─────────────────────────────────────────────────────────── ```bash -git clone /mnt/user/appdata/Varaverk -cd /mnt/user/appdata/Varaverk +git clone /boot/config/plugins/varaverk +cd /boot/config/plugins/varaverk ``` --- @@ -112,7 +112,7 @@ credentials. Set up sparse checkout so each server only receives its own conf fi **On HOST1** — exclude host2.conf: ```bash -cd /mnt/user/appdata/Varaverk +cd /boot/config/plugins/varaverk git sparse-checkout init --no-cone git sparse-checkout set '/*' '!/Configurations/host2.conf' git checkout @@ -120,7 +120,7 @@ git checkout **On HOST2** — exclude host1.conf: ```bash -cd /mnt/user/appdata/Varaverk +cd /boot/config/plugins/varaverk git sparse-checkout init --no-cone git sparse-checkout set '/*' '!/Configurations/host1.conf' git checkout @@ -235,7 +235,7 @@ prompted for HOST1's root password once (for the initial key copy). After that, all SSH is keyless. ```bash -cd /mnt/user/appdata/Varaverk +cd /boot/config/plugins/varaverk bash Partnership/ssh_setup.sh ``` @@ -249,7 +249,7 @@ When prompted, enter HOST1's root password. The script: ### ── Run on HOST1 ────────────────────────────────────────────────────────── ```bash -cd /mnt/user/appdata/Varaverk +cd /boot/config/plugins/varaverk bash Partnership/ssh_setup.sh ``` @@ -296,47 +296,42 @@ ssh -o StrictHostKeyChecking=accept-new root@unRAID-Gmer4Lfe "echo ok" --- -## ━━━ STEP 5: ARBITER — USER SCRIPTS SETUP ━━━ +## ━━━ STEP 5: SCHEDULER SETUP ━━━ -Arbiter (the User Scripts plugin) is the only thing Arbiter runs — never individual -scripts directly. Each entry is an orchestrator that calls everything in its window. - -Open **Settings → User Scripts** in the unRAID WebGUI. +**Array start** uses the User Scripts plugin (one entry only). **Everything else** runs +through the Varaverk plugin's built-in scheduler — configure via the Scheduler tab or +`schedule.json`. Individual scripts are never scheduled directly. --- -### ── Required entries (both servers) ──────────────────────────────────────── +### ── User Scripts — array start only ───────────────────────────────────────── -Create one User Script entry for each row. Set the schedule in the cron field and -paste the command. Name the entry to match the script name. +Open **Settings → User Scripts**. Create one entry: -| Script | Cron schedule | Command | -|--------|--------------|---------| -| `array_started` | At Array Start | `bash /mnt/user/appdata/Varaverk/Orchestrators/array_started.sh` | -| `watchdog_orchestrator` | `* * * * *` | `bash /mnt/user/appdata/Varaverk/Orchestrators/watchdog_orchestrator.sh` | -| `transcode_management` | `*/7 * * * *` | `bash /mnt/user/appdata/Varaverk/Orchestrators/transcode_management.sh` | -| `critical_sync_maintenance` | `*/30 * * * *` | `bash /mnt/user/appdata/Varaverk/Orchestrators/critical_sync_maintenance.sh` | -| `emby_fallback_sync` | `*/30 * * * *` | `bash /mnt/user/appdata/Varaverk/Rsync/rsync.sh /mnt/user/Media_Server/Emby --profile=emby-fallback` | -| `intermediate_sync_maintenance` | `0 */4 * * *` | `bash /mnt/user/appdata/Varaverk/Orchestrators/intermediate_sync_maintenance.sh` | -| `daily_sync_maintenance` | `0 1 * * *` | `bash /mnt/user/appdata/Varaverk/Orchestrators/daily_sync_maintenance.sh` | -| `weekly_sync_maintenance` | `30 2 * * 0` | `bash /mnt/user/appdata/Varaverk/Orchestrators/weekly_sync_maintenance.sh` | -| `weekly_health_digest` | `0 8 * * *` | `bash /mnt/user/appdata/Varaverk/Monitors/weekly_health_digest.sh` | +| Script | Schedule | Command | +|--------|----------|---------| +| `array_started` | At Array Start | `bash /boot/config/plugins/varaverk/Orchestrators/array_started.sh` | -> `array_started` uses the built-in "At Array Start" schedule option in User Scripts — -> it is not a cron expression. - -> `emby_fallback_sync` is the only script with a direct Arbiter entry. It is separate -> from `critical_sync_maintenance` because it needs its own 30-minute slot and Emby -> must stay running during this sync (dirty sync — no container stop). +Set to **Background Task**. This launches everything in ARRAY_START_SCRIPTS. --- -### ── Schedule note ──────────────────────────────────────────────────────────── +### ── Varaverk Scheduler — all cron entries ──────────────────────────────────── -`transcode_management` and `critical_sync_maintenance` both run every 7 and 30 minutes -respectively. In User Scripts, concurrent runs of the same script are prevented by the -lock system (`acquire_lock`) — if the previous run is still active the new one exits -immediately. No need to stagger them manually. +Configure via the Varaverk plugin Scheduler tab (or edit `schedule.json` directly): + +| Script | Cron | Purpose | +|--------|------|---------| +| `transcode_management` | `*/7 * * * *` | Cleanup then manager — order critical | +| `watchdog_orchestrator` | `*/15 * * * *` | resource → docker → system → stability | +| `critical_sync_maintenance` | `*/30 * * * *` | auth + Emby dirty sync + partnership | +| `intermediate_sync_maintenance` | `0 */4 * * *` | arr sync + failed recovery | +| `daily_sync_maintenance` | `0 1 * * *` | full daily maintenance window | +| `weekly_sync_maintenance` | `30 2 * * 0` | clean sync + image updates | +| `monthly_maintenance` | `0 0 15 * *` | ZFS scrub, SMART tests (uptime-gated) | + +Concurrent runs are prevented by `acquire_lock` — if the previous run is still active +the new one exits immediately. No need to stagger entries manually. For the complete schedule and what each orchestrator runs, see [README-Orchestrators.md](Orchestrators/README-Orchestrators.md). @@ -354,7 +349,7 @@ will take a while depending on library size. ```bash # On HOST1 — preview what would sync, check paths and profiles -bash /mnt/user/appdata/Varaverk/Orchestrators/daily_sync_maintenance.sh --dry-run --log +bash /boot/config/plugins/varaverk/Orchestrators/daily_sync_maintenance.sh --dry-run --log ``` Review the output. Check that: @@ -368,11 +363,11 @@ Review the output. Check that: ```bash # On HOST1 — run the full daily sync (this includes rsync for all DAILY_SYNC_SHARES) -bash /mnt/user/appdata/Varaverk/Orchestrators/daily_sync_maintenance.sh --log +bash /boot/config/plugins/varaverk/Orchestrators/daily_sync_maintenance.sh --log ``` This will take longer than future nightly runs — it is transferring everything for -the first time. Monitor progress via the User Scripts output or: +the first time. Monitor progress via the Varaverk log viewer or: ```bash # Watch transfer in real time @@ -381,7 +376,7 @@ watch -n5 'ls -lh /mnt/user/Movies/ | tail -5' After it finishes, also run the critical sync to populate auth and Emby state: ```bash -bash /mnt/user/appdata/Varaverk/Orchestrators/critical_sync_maintenance.sh --log +bash /boot/config/plugins/varaverk/Orchestrators/critical_sync_maintenance.sh --log ``` --- @@ -410,7 +405,7 @@ Commit and pull on both servers so both pick up the change. To start it now without a reboot: ```bash -bash /mnt/user/appdata/Varaverk/Fallback/fallback.sh & +bash /boot/config/plugins/varaverk/Fallback/fallback.sh & ``` --- @@ -437,10 +432,10 @@ simulates an outage using `iptables` — no real downtime, no real data changes. ```bash # On HOST2 — dry run first (sees the sequence, no container starts) -bash /mnt/user/appdata/Varaverk/Fallback/fallback_test.sh --dry-run --log +bash /boot/config/plugins/varaverk/Fallback/fallback_test.sh --dry-run --log # When ready — real test (uses iptables to simulate HOST1 unreachable) -bash /mnt/user/appdata/Varaverk/Fallback/fallback_test.sh --log +bash /boot/config/plugins/varaverk/Fallback/fallback_test.sh --log ``` The test runs in phases — blocks HOST1's Tailscale IP, waits for `fallback.sh` to @@ -478,9 +473,9 @@ HOST2 runs first — it generates its SSH key and waits. The owner completes set ```bash # On HOST2 -bash /mnt/user/appdata/Varaverk/Partnership/partnership_onboard.sh --dry-run --log +bash /boot/config/plugins/varaverk/Partnership/partnership_onboard.sh --dry-run --log # Review output, then: -bash /mnt/user/appdata/Varaverk/Partnership/partnership_onboard.sh --log +bash /boot/config/plugins/varaverk/Partnership/partnership_onboard.sh --log ``` HOST2's work is done after Step 1 (SSH key setup). The rest happens on HOST1. @@ -491,9 +486,9 @@ HOST2's work is done after Step 1 (SSH key setup). The rest happens on HOST1. ```bash # On HOST1 -bash /mnt/user/appdata/Varaverk/Partnership/partnership_onboard.sh --dry-run --log +bash /boot/config/plugins/varaverk/Partnership/partnership_onboard.sh --dry-run --log # Review output — this will deploy auth + arr stacks to HOST2 remotely -bash /mnt/user/appdata/Varaverk/Partnership/partnership_onboard.sh --log +bash /boot/config/plugins/varaverk/Partnership/partnership_onboard.sh --log ``` The owner path deploys containers to HOST2 via SSH, configures WebUI targets, runs @@ -542,8 +537,8 @@ cat /boot/config/fallback_state.db Bandwidth monitor records every sync: ```bash # Latest transfer log -ls -lt /mnt/user/appdata/Varaverk/data/bandwidth_monitor/ -cat /mnt/user/appdata/Varaverk/data/bandwidth_monitor/ +ls -lt /boot/config/plugins/varaverk/data/bandwidth_monitor/ +cat /boot/config/plugins/varaverk/data/bandwidth_monitor/ ``` --- diff --git a/README-User_Script_Plug-in.md b/README-User_Script_Plug-in.md index 1d54f11..f074096 100644 --- a/README-User_Script_Plug-in.md +++ b/README-User_Script_Plug-in.md @@ -2,9 +2,14 @@ # 📋 USER SCRIPTS PLUGIN — COMPLETE SETUP REFERENCE # ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -**Every script entry for the User Scripts plugin — what it does, when it runs, -how to set it up, and what to watch for.** No cross-referencing other READMEs to -understand the basics. The deeper documentation exists — this is your daily reference. +> **Mostly superseded.** Scheduling has moved to the Varaverk plugin's built-in +> scheduler. Only `array_started.sh` still uses User Scripts (for the "At Startup of Array" +> hook). All cron entries are now managed via the Varaverk Scheduler tab or `schedule.json`. +> See `Orchestrators/README-Orchestrators.md` for the current complete schedule. + +**Historical reference for the User Scripts plugin setup — what each script does, +when it ran, how it was configured.** Still useful as a script reference. Paths +updated to reflect current boot-drive installation location. --- @@ -95,7 +100,7 @@ Background: YES — required (starts continuous background processes) ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/array_started.sh +/boot/config/plugins/varaverk/Orchestrators/array_started.sh ``` **What it does:** @@ -133,7 +138,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/transcode_management.sh +/boot/config/plugins/varaverk/Orchestrators/transcode_management.sh ``` **What it does:** @@ -174,7 +179,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/critical_sync_maintenance.sh +/boot/config/plugins/varaverk/Orchestrators/critical_sync_maintenance.sh ``` **What it does:** @@ -207,7 +212,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/arrs_failed_stalled_recovery.sh +/boot/config/plugins/varaverk/Orchestrators/arrs_failed_stalled_recovery.sh ``` **What it does:** @@ -242,7 +247,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/daily_sync_maintenance.sh +/boot/config/plugins/varaverk/Orchestrators/daily_sync_maintenance.sh ``` **What it does:** @@ -309,7 +314,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/weekly_sync_maintenance.sh +/boot/config/plugins/varaverk/Orchestrators/weekly_sync_maintenance.sh ``` **What it does:** @@ -356,7 +361,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Orchestrators/sunday_morning_coffee_report.sh +/boot/config/plugins/varaverk/Orchestrators/sunday_morning_coffee_report.sh ``` **What it does:** @@ -403,7 +408,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/weekly_health_digest.sh +/boot/config/plugins/varaverk/Monitors/weekly_health_digest.sh ``` **What it does:** @@ -435,7 +440,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/system_tuning_monitor.sh +/boot/config/plugins/varaverk/Monitors/system_tuning_monitor.sh ``` **What it does:** @@ -467,7 +472,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/zfs_memory_snapshot.sh +/boot/config/plugins/varaverk/Monitors/zfs_memory_snapshot.sh ``` **What it does:** @@ -493,7 +498,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/smart_health.sh +/boot/config/plugins/varaverk/Monitors/smart_health.sh ``` **What it does:** @@ -524,7 +529,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/cert_monitor.sh +/boot/config/plugins/varaverk/Monitors/cert_monitor.sh ``` **What it does:** @@ -557,7 +562,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/backup_verify.sh +/boot/config/plugins/varaverk/Monitors/backup_verify.sh ``` **What it does:** @@ -591,7 +596,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/emby_session_report.sh +/boot/config/plugins/varaverk/Monitors/emby_session_report.sh ``` **What it does:** @@ -617,7 +622,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Monitors/bandwidth_monitor.sh --report +/boot/config/plugins/varaverk/Monitors/bandwidth_monitor.sh --report ``` **What it does:** @@ -655,7 +660,7 @@ Background: NO (runs and exits — status check) ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Fallback/fallback.sh --status +/boot/config/plugins/varaverk/Fallback/fallback.sh --status ``` **What it does:** @@ -680,7 +685,7 @@ Background: YES — test takes several minutes ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Fallback/fallback_test.sh --dry-run +/boot/config/plugins/varaverk/Fallback/fallback_test.sh --dry-run ``` **What it does:** @@ -753,7 +758,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Rsync/rsync.sh \ +/boot/config/plugins/varaverk/Rsync/rsync.sh \ /mnt/user/appdata-Fallback/Critical-Data ``` @@ -774,7 +779,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Rsync/rsync.sh \ +/boot/config/plugins/varaverk/Rsync/rsync.sh \ /mnt/user/Media_Server/Emby --profile=emby ``` @@ -795,7 +800,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Rsync/rsync.sh \ +/boot/config/plugins/varaverk/Rsync/rsync.sh \ /mnt/user/appdata-Fallback/Arrs_Stack ``` @@ -816,7 +821,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Rsync/rsync.sh \ +/boot/config/plugins/varaverk/Rsync/rsync.sh \ /mnt/user/appdata-Fallback/Important-Data ``` @@ -836,7 +841,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Rsync/rsync.sh \ +/boot/config/plugins/varaverk/Rsync/rsync.sh \ /mnt/user/appdata-Fallback/Gmer4Lfe ``` @@ -849,7 +854,7 @@ No profile container stop required. Incremental — safe to run at any time. ## 🐳 DOCKER_ESSENTIALS ## ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -> **docker_watchdog.sh is called every minute by watchdog_orchestrator.sh — not scheduled separately.** +> **docker_watchdog.sh is called every 15 minutes by watchdog_orchestrator.sh — not scheduled separately.** > docker_daily_restart.sh is called by daily_sync_maintenance.sh. > docker_weekly_restart.sh is called by weekly_sync_maintenance.sh. > docker_network_connect.sh is called by array_started.sh. @@ -868,7 +873,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Watchdogs/docker_watchdog.sh --status +/boot/config/plugins/varaverk/Watchdogs/docker_watchdog.sh --status ``` **What it shows:** @@ -889,7 +894,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Docker_Essentials/watchdog_skip_list_manager.sh --status +/boot/config/plugins/varaverk/Docker_Essentials/watchdog_skip_list_manager.sh --status ``` **What it does:** @@ -928,7 +933,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Docker_Essentials/docker_daily_restart.sh --dry-run +/boot/config/plugins/varaverk/Docker_Essentials/docker_daily_restart.sh --dry-run ``` **What it does:** @@ -955,7 +960,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Docker_Essentials/docker_network_connect.sh --status +/boot/config/plugins/varaverk/Docker_Essentials/docker_network_connect.sh --status ``` **What it does:** @@ -989,7 +994,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Media/media_shares_permissions.sh --dry-run +/boot/config/plugins/varaverk/Media/media_shares_permissions.sh --dry-run ``` **What it does:** @@ -1015,7 +1020,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Media/media_cleaner.sh anime --dry-run +/boot/config/plugins/varaverk/Media/media_cleaner.sh anime --dry-run ``` **What it does:** @@ -1036,7 +1041,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Media/media_cleaner.sh media --dry-run +/boot/config/plugins/varaverk/Media/media_cleaner.sh media --dry-run ``` **What it does:** @@ -1056,7 +1061,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Media/lidarr_cleanup.sh --dry-run --log +/boot/config/plugins/varaverk/Media/lidarr_cleanup.sh --dry-run --log ``` **What it does:** @@ -1088,7 +1093,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Media/sonarr_cleanup.sh --dry-run --log +/boot/config/plugins/varaverk/Media/sonarr_cleanup.sh --dry-run --log ``` **What it does:** @@ -1109,7 +1114,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Media/radarr_cleanup.sh --dry-run --log +/boot/config/plugins/varaverk/Media/radarr_cleanup.sh --dry-run --log ``` **What it does:** @@ -1140,7 +1145,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Transcodes/ramdisk_setup.sh --status +/boot/config/plugins/varaverk/Transcodes/ramdisk_setup.sh --status ``` **What it shows:** @@ -1161,7 +1166,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Transcodes/transcode_manager.sh --status +/boot/config/plugins/varaverk/Transcodes/transcode_manager.sh --status ``` **What it shows:** @@ -1192,7 +1197,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Watchdogs/System/webgui_watchdog.sh +/boot/config/plugins/varaverk/Watchdogs/System/webgui_watchdog.sh ``` **What it does:** @@ -1223,7 +1228,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/unRAID_Essentials/clear_logs.sh +/boot/config/plugins/varaverk/unRAID_Essentials/clear_logs.sh ``` **What it does:** @@ -1250,7 +1255,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Watchdogs/stability_watchdog.sh --status +/boot/config/plugins/varaverk/Watchdogs/stability_watchdog.sh --status ``` **What it shows:** @@ -1271,7 +1276,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/unRAID_Essentials/mover_stop.sh +/boot/config/plugins/varaverk/unRAID_Essentials/mover_stop.sh ``` **What it does:** @@ -1292,7 +1297,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/unRAID_Essentials/rsync_stop.sh --status +/boot/config/plugins/varaverk/unRAID_Essentials/rsync_stop.sh --status ``` **What it does:** @@ -1314,7 +1319,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/unRAID_Essentials/user_scripts_stop.sh --status +/boot/config/plugins/varaverk/unRAID_Essentials/user_scripts_stop.sh --status ``` **What it does:** @@ -1336,7 +1341,7 @@ Background: YES — sequence takes 1-2 minutes ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/unRAID_Essentials/server_reboot.sh --dry-run +/boot/config/plugins/varaverk/unRAID_Essentials/server_reboot.sh --dry-run ``` **What it does:** @@ -1373,7 +1378,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Partnership/partnership_manage.sh --status +/boot/config/plugins/varaverk/Partnership/partnership_manage.sh --status ``` **What it shows:** @@ -1394,7 +1399,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Partnership/partnership_manage.sh --onboard --dry-run +/boot/config/plugins/varaverk/Partnership/partnership_manage.sh --onboard --dry-run ``` **What it does:** @@ -1418,7 +1423,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Partnership/partnership_manage.sh --offboard --dry-run +/boot/config/plugins/varaverk/Partnership/partnership_manage.sh --offboard --dry-run ``` **What it does:** @@ -1452,7 +1457,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Tools/bulk_permissions_repair.sh /mnt/user/Movies --dry-run +/boot/config/plugins/varaverk/Tools/bulk_permissions_repair.sh /mnt/user/Movies --dry-run ``` **What it does:** @@ -1474,7 +1479,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Tools/container_data_export.sh \ +/boot/config/plugins/varaverk/Tools/container_data_export.sh \ Emby /mnt/media-servers/Media_Server/Emby /mnt/user/Backups/ ``` @@ -1499,7 +1504,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Tools/emby_database_repair.sh +/boot/config/plugins/varaverk/Tools/emby_database_repair.sh ``` **What it does:** @@ -1531,7 +1536,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Tools/zfs_pool_scrub.sh +/boot/config/plugins/varaverk/Tools/zfs_pool_scrub.sh ``` **What it does:** @@ -1553,7 +1558,7 @@ Background: YES ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/Tools/recreate_shares.sh --dry-run +/boot/config/plugins/varaverk/Tools/recreate_shares.sh --dry-run ``` **What it does:** @@ -1581,7 +1586,7 @@ Background: NO ```bash #!/bin/bash -/mnt/user/appdata/Varaverk/unRAID_Essentials/git_pull_execute.sh +/boot/config/plugins/varaverk/unRAID_Essentials/git_pull_execute.sh ``` **What it does:** @@ -1607,7 +1612,7 @@ Correct startup setup: Wrong startup setup (old approach): ramdisk_setup — At Startup of Array docker_syslog_filter — At Startup of Array - stability_watchdog — Every Minute via watchdog_orchestrator + stability_watchdog — Every 15 Minutes via watchdog_orchestrator docker_watchdog — At Startup of Array failover — At Startup of Array (unpredictable order, no coordination) diff --git a/README.md b/README.md index 0ade8ad..c6cb93b 100644 --- a/README.md +++ b/README.md @@ -612,7 +612,7 @@ Sunday morning block (6–11am): What actually happens on a typical day, from the ecosystem's perspective: ``` -Throughout the day (every minute via watchdog_orchestrator.sh): +Throughout the day (every 15 minutes via watchdog_orchestrator.sh): resource_watchdog.sh managing: system pressure (throttle/pause/stop) docker_watchdog.sh healing: memory leaks, HTTP failures, required containers system_watchdog.sh watching: system components (storage growth, WebGUI) @@ -858,5 +858,5 @@ Things that are different from what you might expect: ``` Name: Varaverk Repository: git@192.168.50.2:Varaverk/varaverk.git -Install path: /mnt/user/appdata/Varaverk +Install path: /boot/config/plugins/varaverk ``` \ No newline at end of file diff --git a/Tools/Manual-Tools.md b/Tools/Manual-Tools.md index b7c8723..dd9b33c 100644 --- a/Tools/Manual-Tools.md +++ b/Tools/Manual-Tools.md @@ -157,7 +157,7 @@ After fallback_test.sh didn't complete cleanly After a failed handback → state shows FALLBACK but remote is back up and containers are split -After killing fallback.sh directly (not via User Scripts Abort) +After killing fallback.sh directly (not gracefully via SIGTERM) → state is unknown, cycle was interrupted mid-operation After a dev/debug session