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

fix Failover→Fallback naming and missing/stale script references

Browse Source 
Failover/ was renamed to Fallback/ — all script paths and README links
updated across README.md, Orchestrators README, and User Script Plug-in README.

array_start.sh → array_started.sh in Orchestrators scripts table (wrong name).

fallback_state_reset.sh: script is referenced in User Script Plug-in README
but does not exist in Fallback/. Entry updated to document it as not yet built
and provides the manual workaround (direct state file write).

Note: /mnt/user/appdata-Failover/ share path references left unchanged —
that is the actual unRAID share name on the server, not the script folder.
This commit is contained in:
Gmer4Lfe
2026-05-22 21:47:03 -04:00
parent 8b0ee44b65
commit 8d72fbf0e2
3 changed files with 20 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README-User_Script_Plug-in.md
+16 -21
View File
@@ -675,7 +675,7 @@ Background: NO (runs and exits — status check)
```bash
#!/bin/bash
/mnt/user/appdata/unraid_scripts/Failover/failover.sh --status
/mnt/user/appdata/unraid_scripts/Fallback/fallback.sh --status
```
**What it does:**
@@ -700,7 +700,7 @@ Background: YES — test takes several minutes
```bash
#!/bin/bash
/mnt/user/appdata/unraid_scripts/Failover/failover_test.sh --dry-run
/mnt/user/appdata/unraid_scripts/Fallback/fallback_test.sh --dry-run
```
**What it does:**
@@ -721,31 +721,26 @@ Change `--dry-run` to nothing and run during a maintenance window.
---
### ── failover_state_reset ────────────────────────────────────────────────────
### ── fallback_state_reset ────────────────────────────────────────────────────
```
Category: Failover
Name: failover_state_reset
Schedule: None — run manually (after testing or failed handback)
Background: NO
```
> **Not yet built.** `fallback_state_reset.sh` is a planned utility — not in `Fallback/` yet.
>
> **Manual workaround** when state file is stuck in FAILOVER after a failed test or
> forced kill of fallback.sh:
> ```bash
> # Verify first — right containers on right server, DDNS correct, fallback.sh not running
> cat /boot/config/fallback_state.db
> echo "state=NORMAL" > /boot/config/fallback_state.db
> ```
> Resets state only — does NOT start or stop any containers.
```bash
#!/bin/bash
/mnt/user/appdata/unraid_scripts/Failover/failover_state_reset.sh --status
```
**What it does:**
Shows current state file then prompts for confirmation before resetting to NORMAL.
Resets state file only — does NOT start or stop any containers.
**When to use:**
**When you need this:**
State file stuck in FAILOVER after a test that didn't complete cleanly. After killing
failover.sh directly (not via plugin Abort button). After a failed handback.
fallback.sh directly (not via plugin Abort button). After a failed handback.
**Verify before resetting:**
Right containers on right server. DDNS correct (`nslookup Gmer4Lfe.com`).
Both servers Tailscale connected. failover.sh not currently running.
Both servers Tailscale connected. fallback.sh not currently running.
---