Failed to start borgmatic backup. #480
Labels
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
borgmatic-collective/borgmatic#480
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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
Steps to reproduce (if a bug)
I don't really know if this a bug or just my config error, borgmatic.service won't start.
Actual behavior (if a bug)
Expected behavior (if a bug)
Other notes / implementation ideas
Environment
borgmatic version: [1.5.20]
Use
sudo borgmatic --versionorsudo pip show borgmatic | grep ^Versionborgmatic installation method: [e.g., Debian package, Docker container, etc.]
Borg version: [1.1.17]
Use
sudo borg --versionPython version: [3.9.7]
Use
python3 --versionDatabase version (if applicable): [version here]
Use
psql --versionormysql --versionon client and server.operating system and version: [Fedora Server 33]
Thanks for reporting this! Looks like there are two issues here:
Looking past the second issue for the moment, are you able to see an issue on or around line 142 of your configuration? Feel free to upload here if you'd like assistance debugging.
@witten Thank you for your reply. I have set encryption passphrase on line 142 take look this screenshot if there is a syntax error on my config.
It looks like you may be missing the underscore in
encryption_passphrase? Same forcheckpoint_interval. I'm guessing that's the issue!Nope, the screenshot had taken from "nano" editor thats why it is not showing up.
Ah, gotcha. At this point, I think I'll need to see the entire configuration file (not just a screenshot) in order to debug this further. Please feel free to redact passphrases of course and any other sensitive information. And thank you for your patience!
Thanks a lot I will share it to you my config file, this is my first time trying borgmatic so please suggest me any corrections on my setup.
You can check my config file here
Thanks for sharing that! Looking at your config file, there are a few problems I've found:
storage:is commented out even though there are options configured in thestoragesection. (The fix is to remove the#beforestorage:.)hooks:is commented out even though there are options configured in thehookssection.- echo "Starting a backup."but the corresponding hook keys are commented out. For instancebefore_backup:,before_prune:, and so on are commented out, even though they shouldn't be when a value is present.Hope that helps!
Thanks a lot I fixed that and did "systemctl daemon-reload" and "systemctl start borgmatic.service" and unfortunately it seems there is still a problem in my config file... Line 5 is (Location) and Line 127 is (Storage) option.
Could I get a peek at your updated configuration file (redacted)? My guess is there's a spacing issue, where some of the options aren't lined up in a section. We're seeing something similar over on #482.
Thank you @witten here is my config file,
https://mega.nz/file/FMJQgRgY#ZKGMt1iA9iPejcE18YA0shoLTvb8S2zyE0zCKsCB6Y8
It indeed looks like a spacing issue. Both the
storage:and thehooks:section keys should not have any spaces right before them. I believe if you make those changes, the problem will be fixed!@witten thank you so much and am sorry for taking your time. Now its working for me.
No worries.. I'm glad it's all sorted out now! At the very least, it helps to see what kinds of issues folks are running into.