From dda97505d83dbf5fe6cc2d2f134891d1267425e1 Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Mon, 11 Dec 2023 08:42:04 -0800 Subject: [PATCH] Add hints to borg backup error logging I spent a number of hours recently trying to debug why mysqldump stopped working. In reality it appears that the problem was borg-backup's ssh connectivity causing the mysql-dump to not be able to stream properly. Add a logging note about checking the other half of backup streaming when the streaming script fails to try and make it more obvious this may ocurr. Change-Id: Idf53fc9e61f05077b954d730d88beab0cc1db09b --- playbooks/roles/borg-backup/templates/borg-backup.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/playbooks/roles/borg-backup/templates/borg-backup.j2 b/playbooks/roles/borg-backup/templates/borg-backup.j2 index f5a24df369..fa1289a529 100644 --- a/playbooks/roles/borg-backup/templates/borg-backup.j2 +++ b/playbooks/roles/borg-backup/templates/borg-backup.j2 @@ -46,6 +46,7 @@ do _status=( "${PIPESTATUS[@]}" ) if [[ ${_status[0]} -ne 0 ]]; then info "Streaming script ${f} failed!" + info "Note that problems in the ssh connectivity might cause the streaming script to fail. You may need to check both halves of the streaming backup." stream_exit=${_status[0]} elif [[ ${_status[1]} -ne 0 ]]; then info "Borg failed (rc: ${_status[1]})!"