Running the check for much longer to see if it breaks the loop itself or actually finishes.It looks suspicious, but I cannot confirm that the “creation date” it has listed (which is the day the repo was made) would include modifications to this file, so I’m at a bit of a loss.
Opened up the Backblaze B2 bucket to see what the config file had in it. I doubled checked the Backblaze keys to see if they expired, but they are definitely still valid. Looked in the forums a bit longer, tried again (about a minute) with the -no-cache option, received the same config file error above. Looked through the forums a bit, started by checking for hardware-related bottlenecks, but I still have more than half of my Ram (8GB remaining), storage, and swap space available so I am doubt that’s the issue. The only error I got was “Fatal: Unable to open config file. Next I tried to run the restic check command in CLI to check for errors, but after waiting about 15 minutes with the verbose switch I aborted it. At first I thought this might just be a fluke run, so I restarted the PC and finished the rest of the updates. When I update the server, I often run the script again which will see if restic check fails, and if it does it assumes it is a first-time run and will init the remote repo. This script also sets up the systemd service that does the backup script in the first place, which runs restic check, backup, and prune, reporting any errors and timing out if restic check takes more than a few minutes. 
Backblaze installer hangs install#
I have an initial install script for Restic through Ansible that handles setting up environment variables and connecting to the right repository in Backblaze B2. Since then I’ve been trying to figure out what went wrong, below is my setup, what I’ve tried, and what I suspect happened.
The good news is I still have all data I care about that Restic backed up here in my home server, but I want to fix this ASAP since this is my only off-site backup. I’ve been using Restic without incident since February, and I went to my server to do some routine security updates and the next day Restic failed to backup.
0 kommentar(er)
