Document today's restructures, and give data/ a README that ships with it
This commit is contained in:
@@ -521,7 +521,7 @@ at `$PERSISTENT_CONF_CACHE` while the partner is offline.
|
||||
**Remote online:** removes the persistent backup if one exists. It is not needed —
|
||||
`conf_sync.sh` will pull a fresh copy on the next boot. Silent when backup is already absent.
|
||||
|
||||
**Remote offline:** copies partner confs from the RAM cache (`/tmp/.cache/vv/d/`) to
|
||||
**Remote offline:** copies partner confs from the RAM cache (`$CONF_RAM_CACHE_DIR`, `/tmp/varaverk/conf/`) to
|
||||
`$PERSISTENT_CONF_CACHE`. Runs every 15 minutes, so the backup stays current throughout
|
||||
an extended outage. If this host reboots while the partner is still down,
|
||||
`conf_cache_restore.sh` will load the backup into RAM and fallback.sh will have
|
||||
@@ -821,8 +821,8 @@ storage_watchdog.sh --status
|
||||
### stability_watchdog Rebooted Unexpectedly
|
||||
|
||||
```bash
|
||||
# Check the reboot log (survives reboots — in State_Files/):
|
||||
cat /boot/config/plugins/varaverk/State_Files/system_watchdog_reboots.db
|
||||
# Check the reboot log (survives reboots — in data/state/):
|
||||
cat /boot/config/plugins/varaverk/data/state/system_watchdog_reboots.db
|
||||
# Shows timestamp and reason for each watchdog-triggered reboot
|
||||
|
||||
# Check syslog near the reboot time:
|
||||
|
||||
Reference in New Issue
Block a user