summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-04-21 11:53:02 +0300
committerPaul Buetow <paul@buetow.org>2024-04-21 11:53:02 +0300
commit6a8bd13a159aa3d6880143b79c9d9ad4dd2beace (patch)
tree10910c961bab0a66c3a0f97f86cda3f60efa67c5
parentfd8ba0affe3aee93dcfeab9a9e8007cb1633401f (diff)
Update content for gemtext
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi8
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl5
-rw-r--r--gemfeed/atom.xml10
-rw-r--r--index.gmi2
-rw-r--r--uptime-stats.gmi2
5 files changed, 12 insertions, 15 deletions
diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi
index 679fa362..a442b59a 100644
--- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi
+++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi
@@ -33,13 +33,10 @@ Table of contents:
My auto-failover requirements
My HA solution
Only OpenBSD base installation required
- !/bin/ksh
- Race condition (e.g. script execution aborted in the middle of the previous run)
Fairly cheap and geo-redundant
Failover time and split-brain
Failover support for multiple protocols
Let's encrypt TLS certificates
- Weekly auto-failover for Let's Encrypt automation
Monitoring
Rex automation
More HA
@@ -159,7 +156,8 @@ transform () {
After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed:
```sh
-# Race condition (e.g. script execution aborted in the middle of the previous run)
+#! Race condition !#
+
if [ -f $zone_file.bak ]; then
mv $zone_file.bak $zone_file
fi
@@ -252,7 +250,7 @@ As a solution, the CRON job responsible for the DNS failover also checks for the
Which translates to:
```sh
-# Weekly auto-failover for Let's Encrypt automation
+#! Weekly auto-failover for Let's Encrypt automation !#
local -i -r week_of_the_year=$(date +%U)
if [ $(( week_of_the_year % 2 )) -eq 0 ]; then
local tmp=$master
diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl
index 71133853..f922799a 100644
--- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl
+++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl
@@ -143,7 +143,8 @@ transform () {
After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed:
```sh
-# Race condition (e.g. script execution aborted in the middle of the previous run)
+#! Race condition !#
+
if [ -f $zone_file.bak ]; then
mv $zone_file.bak $zone_file
fi
@@ -236,7 +237,7 @@ As a solution, the CRON job responsible for the DNS failover also checks for the
Which translates to:
```sh
-# Weekly auto-failover for Let's Encrypt automation
+#! Weekly auto-failover for Let's Encrypt automation !#
local -i -r week_of_the_year=$(date +%U)
if [ $(( week_of_the_year % 2 )) -eq 0 ]; then
local tmp=$master
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index d1503b37..8763cb06 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
- <updated>2024-04-21T11:44:45+03:00</updated>
+ <updated>2024-04-21T11:52:49+03:00</updated>
<title>foo.zone feed</title>
<subtitle>To be in the .zone!</subtitle>
<link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -53,13 +53,10 @@ Table of contents:
My auto-failover requirements
My HA solution
Only OpenBSD base installation required
- !/bin/ksh
- Race condition (e.g. script execution aborted in the middle of the previous run)
Fairly cheap and geo-redundant
Failover time and split-brain
Failover support for multiple protocols
Let&#39;s encrypt TLS certificates
- Weekly auto-failover for Let&#39;s Encrypt automation
Monitoring
Rex automation
More HA
@@ -192,7 +189,8 @@ http://www.gnu.org/software/src-highlite -->
by Lorenzo Bettini
http://www.lorenzobettini.it
http://www.gnu.org/software/src-highlite -->
-<pre><i><font color="#9A1900"># Race condition (e.g. script execution aborted in the middle of the previous run)</font></i>
+<pre><i><font color="#9A1900">#! Race condition !#</font></i>
+
<b><font color="#0000FF">if</font></b> <font color="#990000">[</font> -f <font color="#009900">$zone_file</font><font color="#990000">.</font>bak <font color="#990000">];</font> <b><font color="#0000FF">then</font></b>
mv <font color="#009900">$zone_file</font><font color="#990000">.</font>bak <font color="#009900">$zone_file</font>
<b><font color="#0000FF">fi</font></b>
@@ -289,7 +287,7 @@ echo <font color="#FF0000">"Failover of zone $zone to $MASTER completed"</font>
by Lorenzo Bettini
http://www.lorenzobettini.it
http://www.gnu.org/software/src-highlite -->
-<pre><i><font color="#9A1900"># Weekly auto-failover for Let's Encrypt automation</font></i>
+<pre><i><font color="#9A1900">#! Weekly auto-failover for Let's Encrypt automation !#</font></i>
<b><font color="#0000FF">local</font></b> -i -r <font color="#009900">week_of_the_year</font><font color="#990000">=</font><font color="#009900">$(</font>date <font color="#990000">+%</font>U<font color="#990000">)</font>
<b><font color="#0000FF">if</font></b> <font color="#990000">[</font> <font color="#009900">$(</font><font color="#990000">(</font> week_of_the_year <font color="#990000">%</font> <font color="#993399">2</font> <font color="#990000">))</font> -eq <font color="#993399">0</font> <font color="#990000">];</font> <b><font color="#0000FF">then</font></b>
<b><font color="#0000FF">local</font></b> <font color="#009900">tmp</font><font color="#990000">=</font><font color="#009900">$master</font>
diff --git a/index.gmi b/index.gmi
index 9d83a3bd..eb74640e 100644
--- a/index.gmi
+++ b/index.gmi
@@ -1,6 +1,6 @@
# foo.zone
-> This site was generated at 2024-04-21T11:44:45+03:00 by `Gemtexter`
+> This site was generated at 2024-04-21T11:52:49+03:00 by `Gemtexter`
```
|\---/|
diff --git a/uptime-stats.gmi b/uptime-stats.gmi
index e0b9bb27..58247183 100644
--- a/uptime-stats.gmi
+++ b/uptime-stats.gmi
@@ -1,6 +1,6 @@
# My machine uptime stats
-> This site was last updated at 2024-04-21T11:44:45+03:00
+> This site was last updated at 2024-04-21T11:52:49+03:00
The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine.