Use logrotate for backrest logging rather than nuking immediately

Just in case something goes wrong with healthchecks
This commit is contained in:
Jake Howard 2021-06-27 10:58:01 +01:00
parent 8696f6d93f
commit 41a8fe3b4d
Signed by: jake
GPG key ID: 57AFB45680EDD477
3 changed files with 15 additions and 2 deletions

View file

@ -0,0 +1,8 @@
/home/restic/log/* {
weekly
rotate 12
missingok
compress
nodateext
notifempty
}

View file

@ -20,7 +20,6 @@ cron_backup() {
restic --verbose backup {{ restic_backup_locations|join(' ') }} &> | tee -a $RESTIC_LOG_FILE restic --verbose backup {{ restic_backup_locations|join(' ') }} &> | tee -a $RESTIC_LOG_FILE
exit_code=${PIPESTATUS[0]} exit_code=${PIPESTATUS[0]}
curl -fsS -m 10 --retry 5 -o /dev/null {{ healthchecks_host }}/{{ restic_healthchecks_id }}/$exit_code --data-binary "@$RESTIC_LOG_FILE" curl -fsS -m 10 --retry 5 -o /dev/null {{ healthchecks_host }}/{{ restic_healthchecks_id }}/$exit_code --data-binary "@$RESTIC_LOG_FILE"
rm $RESTIC_LOG_FILE
echo "Exit code: $exit_code" echo "Exit code: $exit_code"
} }
@ -36,7 +35,6 @@ cron_forget() {
restic forget --prune $FORGET_OPTIONS &> | tee -a $RESTIC_LOG_FILE restic forget --prune $FORGET_OPTIONS &> | tee -a $RESTIC_LOG_FILE
exit_code=${PIPESTATUS[0]} exit_code=${PIPESTATUS[0]}
curl -fsS -m 10 --retry 5 -o /dev/null {{ healthchecks_host }}/{{ restic_forget_healthchecks_id }}/$exit_code --data-binary "@$RESTIC_LOG_FILE" curl -fsS -m 10 --retry 5 -o /dev/null {{ healthchecks_host }}/{{ restic_forget_healthchecks_id }}/$exit_code --data-binary "@$RESTIC_LOG_FILE"
rm $RESTIC_LOG_FILE
echo "Exit code: $exit_code" echo "Exit code: $exit_code"
} }
{% endif %} {% endif %}

View file

@ -51,3 +51,10 @@
user: restic user: restic
become: true become: true
when: restic_forget when: restic_forget
- name: backrest fail2ban config
template:
src: files/backrest-logrotate
dest: /etc/logrotate.d/backrest
mode: "0600"
become: true