From: Peter Palfrader <peter@palfrader.org>
Date: Mon, 5 Feb 2018 09:03:10 +0000 (+0100)
Subject: Document how to fix BASE-IS-OLD
X-Git-Url: https://git.adam-barratt.org.uk/?p=mirror%2Fdsa-wiki.git;a=commitdiff_plain;h=4748598a49ca95a8569fb7638db087e00821ddeb;hp=422c89a14dfbdaec6c67de08faa8e493ebc2389f

Document how to fix BASE-IS-OLD
---

diff --git a/input/howto/postgres-backup.creole b/input/howto/postgres-backup.creole
index b897514..fee97c6 100644
--- a/input/howto/postgres-backup.creole
+++ b/input/howto/postgres-backup.creole
@@ -50,3 +50,19 @@ https://www.postgresql.org/docs/9.4/static/continuous-archiving.html
 
 * Test running "postgres-make-base-backups host:port".
 * You should see a tarball and WALs
+
+= Nagios warnings =
+
+== BASE-IS-OLD ==
+
+(2018-02) Our nagios check warns us when a backup server has not successfully fetched
+a base backup recently.  The causes often are that either the postgres server or the
+backup host went down or was down during the time of the weekly cronjob.
+
+To re-run a base backup for a specific cluster, log into the backup server
+(either storace or backuphost), cat /usr/local/bin/postgres-make-base-backups
+to see the port for the cluster, and run
+{{{
+  sudo -u debbackup /usr/local/bin/postgres-make-base-backups <host>:<port>
+}}}
+probably best to do that in a screen as it might take a while.