Update all docs to reflect watchdog restructure

README-Watchdogs.md: new tier diagram, updated script table, execution flow,
  state file table, and folder relationship diagram
Manual-Watchdogs.md: added system_watchdog (thin), System/storage_watchdog,
  System/webgui_watchdog, and stability_watchdog sections; updated TOC and troubleshooting
README.md: updated schedule listing, folder description, daily cycle examples
README-User_Script_Plug-in.md: stability_watchdog references throughout
unRAID_Essentials/README + Manual: stability_watchdog, updated storage path
Monitors/README, Rsync/Manual, Tools/Manual: lock name list updates
This commit is contained in:
Gmer4Lfe
2026-05-22 20:26:36 -04:00
parent cf21efaeea
commit 13ce8497f3
9 changed files with 150 additions and 77 deletions
+8 -8
View File
@@ -111,14 +111,14 @@ docker_syslog_filter.sh — suppresses Docker veth noise before containers crea
php_fpm_max_children.sh — sets PHP-FPM workers to 250 before WebGUI serves requests
ramdisk_setup.sh — creates /mnt/ramdisk_transcodes and symlink before Emby starts
docker_network_connect.sh— ensures custom networks exist + containers connected
system_watchdog.sh ← continuous — three-tier server stability watchdog
stability_watchdog.sh ← last-resort — three-tier server stability watchdog
docker_watchdog.sh ← continuous — two-tier container healing watchdog
failover.sh ← continuous — mutual failover state machine
```
**After running:**
One-shot scripts exit cleanly. Three continuous processes run in the background until
the array stops. Check with: `pgrep -f "system_watchdog\|docker_watchdog\|failover"`
the array stops. Check with: `pgrep -f "stability_watchdog\|docker_watchdog\|failover"`
---
@@ -899,7 +899,7 @@ Background: NO
**What it shows:**
Strike counts for all monitored containers. Current skip list with running/stopped state.
Whether startup grace period is active and how long remains. Whether RAM emergency
deferral is active (mem_shutdown_active from system_watchdog). Last cycle timing.
deferral is active (mem_shutdown_active from stability_watchdog). Last cycle timing.
---
@@ -1200,7 +1200,7 @@ flip count, session split ramdisk vs SSD).
## 🖥️ UNRAID_ESSENTIALS
## ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> **system_watchdog.sh is started by array_start.sh — not scheduled separately.**
> **stability_watchdog.sh is called by watchdog_orchestrator.sh — not scheduled separately.**
> **webgui_watchdog.sh, system_tuning_monitor.sh, clear_logs.sh are scheduled below.**
> **inotify_tuning.sh, php_fpm_max_children.sh, docker_syslog_filter.sh run via array_start.sh.**
@@ -1264,11 +1264,11 @@ Active containers like Emby and SABnzbd grow fastest. Truncation not rotation
---
### ── system_watchdog_status ──────────────────────────────────────────────────
### ── stability_watchdog_status ──────────────────────────────────────────────────
```
Category: unRAID_Essentials
Name: system_watchdog_status
Name: stability_watchdog_status
Schedule: None — run manually
Background: NO
```
@@ -1632,7 +1632,7 @@ Correct startup setup:
Wrong startup setup (old approach):
ramdisk_setup — At Startup of Array
docker_syslog_filter — At Startup of Array
system_watchdog — At Startup of Array
stability_watchdog — Every Minute via watchdog_orchestrator
docker_watchdog — At Startup of Array
failover — At Startup of Array
(unpredictable order, no coordination)
@@ -1707,5 +1707,5 @@ critical_sync_maintenance verify Critical-Data sync completes to HOST2
daily_sync_maintenance --dry-run verify remote connectivity and share list
failover_status confirm NORMAL state on both servers
docker_watchdog_status confirm required containers all running
system_watchdog_status confirm no threshold alerts on first check
stability_watchdog_status confirm no threshold alerts on first check
```