From e72d00499dc2e61b2e48fffbf6de5784835675e5 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 4 Jan 2026 00:06:45 +0200 Subject: Update content for gemtext --- gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi | 8 ++------ gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl | 8 ++------ gemfeed/atom.xml | 10 +++------- 3 files changed, 7 insertions(+), 19 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi index b6886095..157951a9 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi @@ -1388,6 +1388,8 @@ Auto-failback ENABLED (removed /data/nfs/nfs.NO_AUTO_FAILBACK) When `f0` reboots (planned or unplanned), `f1` takes over as CARP MASTER. To ensure `f0` automatically reclaims its primary role once it's fully operational, we'll implement an automatic failback mechanism. With: +> Update: Fixed the script at Sun 4 Jan 00:04:28 EET 2026 - removed the NFS service check because when f0 is BACKUP, NFS services are intentionally stopped by carpcontrol.sh, which would prevent auto-failback from ever triggering. + ```sh paul@f0:~ % doas tee /usr/local/bin/carp-auto-failback.sh <<'EOF' #!/bin/sh @@ -1427,12 +1429,6 @@ if [ -f "$BLOCK_FILE" ]; then exit 0 fi -# Check if NFS services are running (ensure we're fully ready) -if ! service nfsd status >/dev/null 2>&1; then - log_message "SKIP: NFS services not yet running" - exit 0 -fi - # All conditions met - promote to MASTER log_message "CONDITIONS MET: Promoting to MASTER (was $CURRENT_STATE)" /usr/local/bin/carp master diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl index 1bf1fde7..444dcafe 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl @@ -1331,6 +1331,8 @@ Auto-failback ENABLED (removed /data/nfs/nfs.NO_AUTO_FAILBACK) When `f0` reboots (planned or unplanned), `f1` takes over as CARP MASTER. To ensure `f0` automatically reclaims its primary role once it's fully operational, we'll implement an automatic failback mechanism. With: +> Update: Fixed the script at Sun 4 Jan 00:04:28 EET 2026 - removed the NFS service check because when f0 is BACKUP, NFS services are intentionally stopped by carpcontrol.sh, which would prevent auto-failback from ever triggering. + ```sh paul@f0:~ % doas tee /usr/local/bin/carp-auto-failback.sh <<'EOF' #!/bin/sh @@ -1370,12 +1372,6 @@ if [ -f "$BLOCK_FILE" ]; then exit 0 fi -# Check if NFS services are running (ensure we're fully ready) -if ! service nfsd status >/dev/null 2>&1; then - log_message "SKIP: NFS services not yet running" - exit 0 -fi - # All conditions met - promote to MASTER log_message "CONDITIONS MET: Promoting to MASTER (was $CURRENT_STATE)" /usr/local/bin/carp master diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 035bfbc6..708635df 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2026-01-03T23:57:42+02:00 + 2026-01-04T00:05:40+02:00 foo.zone feed To be in the .zone! @@ -7962,6 +7962,8 @@ Auto-failback ENABLED (removed /data/nfs/nfs.NO_AUTO_FAILBACK)
When f0 reboots (planned or unplanned), f1 takes over as CARP MASTER. To ensure f0 automatically reclaims its primary role once it's fully operational, we'll implement an automatic failback mechanism. With:

+Update: Fixed the script at Sun 4 Jan 00:04:28 EET 2026 - removed the NFS service check because when f0 is BACKUP, NFS services are intentionally stopped by carpcontrol.sh, which would prevent auto-failback from ever triggering.
+