returned non-zero exit status 2 #519
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#519
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
when run borgmatic
Steps to reproduce (if a bug)
Include (sanitized) borgmatic configuration files if applicable.
Actual behavior (if a bug)
also
Environment
borgmatic version: [version here]
1.5.13
borgmatic installation method: [e.g., Debian package, Docker container, etc.]
pip
Borg version: [version here]
borg 1.1.9
Python version: [version here]
Python 3.7.3
operating system and version: [OS here]
Debia buster
Have you tried increasing borgmatic's verbosity, e.g. with the
--verbosity 2flag to show more information in the logs? If that doesn't help, you can also try running theborgcommand directly (e.g. copy and paste the command borgmatic is showing) to see if there's a more useful error message. You shouldn't have to do that, but borgmatic may be suppressing something.I will try it. But it happens time to time by cron.
You can up the verbosity when borgmatic is run via cron as well! Same flags.
When you do get these errors from cron, is there anything else of note in the borgmatic logs? Feel free to paste here or link to a paste of your logs elsewhere.
borg create --exclude-from /tmp/tmpm6ad0ity --exclude-caches --exclude-if-present .nobackup --compression auto,zstd --one-file-system --debug --show-rc xxxxx@xxxxx.repo.borgbase.com:repo::{hostname}-{now} /var/www
Ah, unfortunately this likely isn't the same error that's tripping up borgmatic. In this case, Borg is failing to read the temporary excludes file that borgmatic uses to pass your configured excludes to Borg. But that probably wouldn't be the case when run via borgmatic. If you leave out
--exclude-from /tmp/tmpm6ad0ityand run the same command, do you get any error? (Note that your excludes won't be passed in that way!)if i leave out
--exclude-from /tmp/tmpm6ad0ityit works.Okay, in that case the issue might be with borgmatic. I'd recommend to going back to your borgmatic cron invocation and adding
--verbosity 2and seeing if the resulting cron error logs show anything useful.Hi
I have two repos.
Is there anything else in the logs? That looks like a successful run without any errors.. Borg is exiting each time with exit code 0 (success).
Hi, thanks!
Not really.
From borgase dashboard: "this repo was not modified within a day"
I will log one more day with syslog and go back
I only see one repo in that log (
c036v49y@c036v49y.repo.server.tld:repo), so unless that resolves to Borgbase, I wouldn't expect anything in Borgbase to be modified. You said you have two repos though. If you post your borgmatic configuration (with anything redacted you don't want to share), I'd be happy to take a look.c036v49y and q4nudxni
config
Everything there looks correct to me for two repos. It's possible that Borg/borgmatic just haven't finished running though, and therefore the logs aren't yet complete.
You are right
That's looking like an error from Borg, specifically a problem with your network connection to the remote repository's server. You could try the work-around described here: https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#broken-pipe-with-remote-repository
Thank you very much. I will try your suggestion. I wonder why this only happens with a single repository.
Could be a server with slower or less reliable connectivity?
I'm closing this for now, but if you have any follow-ups, please feel free to post them here! I'm happy to reopen if needed.
Thanks, @witten. You are right. It was the networking setup
Awesome, I'm glad to hear it!