Local exception, borg create returned non-zero exit status 2. #465
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#465
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Complete the initial backup through a docker container (running on Unraid). The previous backup failed midway through for the same error code.
Command I'm trying to run:
Steps to reproduce (if a bug)
Include (sanitized) borgmatic configuration files if applicable.
Config file:
Actual behavior (if a bug)
Include (sanitized)
--verbosity 2
output if applicable.Log file:
Expected behavior (if a bug)
Backup completes successfully.
Other notes / implementation ideas
Environment
borgmatic version: 1.5.18
Use
sudo borgmatic --version
orsudo pip show borgmatic | grep ^Version
borgmatic installation method: Docker container
Borg version: 1.1.17
Use
sudo borg --version
Python version: 3.8.10
Use
python3 --version
Database version (if applicable): psql (PostgreSQL) 13.4
Use
psql --version
ormysql --version
on client and server.operating system and version: Unraid 6.9.2, Docker version 20.10.5
Local exception, borg create returned non-zero exist status 2.to Local exception, borg create returned non-zero exit status 2.Thanks for the detailed issue write-up! What's weird in the log is that Borg is definitely erroring (exit code 2), and I see that there's a traceback, but I can't find the details of the traceback anywhere in the log. So here's my recommendation: Run Borg directly and see if you get any more useful output—like the actual contents of the Borg traceback. Conveniently, your borgmatic log contains the full Borg command it's running (minus any environment variables for things like encryption passphrases), so you should hopefully be able to reproduce the problem pretty easily.
Let me know what you find!
Thanks, don't know why I didn't think to run that. Here's the actual error if you were curious:
However, this is odd because Unraid shows 12.7 TB free, as does a df -h:
I suppose it isn't an issue with Borgmatic, though!
Bingo! Here's my issue:
Ref:
https://github.com/borgbackup/borg/issues/3994
Closing for now!