You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we mostly use it as single-backup, the image supports being run for a long time as it records cron jobs.
Long-running containers would initialize the borg repo (using the bitwarden credentials) upon start and just run borgmatic on every job started by cron.
Should borgbase configuration have changed since the start of the container, the borgmatic tasks would keep failing.
This happened with wp1 project where the container ran for 7 weeks but borgbase's target server changed in between. It resulted in container that keeps on launching the same task which always fails because the remote end changed.
Remote: ssh: Could not resolve hostname [box-eu16.borgbase.com](http://box-eu16.borgbase.com/): Name or service not known
As this is a first and it is now recorded in the ticket, let's wait and see if that is a frequent enough issue for us to fix it.
The text was updated successfully, but these errors were encountered:
While we mostly use it as single-backup, the image supports being run for a long time as it records cron jobs.
Long-running containers would initialize the borg repo (using the bitwarden credentials) upon start and just run borgmatic on every job started by cron.
Should borgbase configuration have changed since the start of the container, the borgmatic tasks would keep failing.
This happened with
wp1
project where the container ran for 7 weeks but borgbase's target server changed in between. It resulted in container that keeps on launching the same task which always fails because the remote end changed.As this is a first and it is now recorded in the ticket, let's wait and see if that is a frequent enough issue for us to fix it.
The text was updated successfully, but these errors were encountered: