Failed to start borgmatic backup. #480

Closed
opened 8 months ago by elhananjair · 13 comments

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 --version or sudo pip show borgmatic | grep ^Version

borgmatic installation method: [e.g., Debian package, Docker container, etc.]

Borg version: [1.1.17]

Use sudo borg --version

Python version: [3.9.7]

Use python3 --version

Database version (if applicable): [version here]

Use psql --version or mysql --version on client and server.

operating system and version: [Fedora Server 33]

#### 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 --version` or `sudo pip show borgmatic | grep ^Version` **borgmatic installation method:** [e.g., Debian package, Docker container, etc.] **Borg version:** [1.1.17] Use `sudo borg --version` **Python version:** [3.9.7] Use `python3 --version` **Database version (if applicable):** [version here] Use `psql --version` or `mysql --version` on client and server. **operating system and version:** [Fedora Server 33]
Owner

Thanks for reporting this! Looks like there are two issues here:

  1. There's a legitimate problem with your borgmatic configuration file at line 142, column 7 with "did not find an expected key".
  2. The borgmatic error handling code is not handling this problem gracefully and blowing up with a traceback. (This is a bug.)

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.

Thanks for reporting this! Looks like there are two issues here: 1. There's a legitimate problem with your borgmatic configuration file at line 142, column 7 with "did not find an expected key". 2. The borgmatic error handling code is not handling this problem gracefully and blowing up with a traceback. (This is a bug.) 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 added the
bug
label 8 months ago

Thanks for reporting this! Looks like there are two issues here:

  1. There's a legitimate problem with your borgmatic configuration file at line 142, column 7 with "did not find an expected key".
  2. The borgmatic error handling code is not handling this problem gracefully and blowing up with a traceback. (This is a bug.)

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.
image

> Thanks for reporting this! Looks like there are two issues here: > > 1. There's a legitimate problem with your borgmatic configuration file at line 142, column 7 with "did not find an expected key". > 2. The borgmatic error handling code is not handling this problem gracefully and blowing up with a traceback. (This is a bug.) > > 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. ![image](/attachments/3a08187b-4a0c-4321-824d-27d70f526f20)
Owner

It looks like you may be missing the underscore in encryption_passphrase? Same for checkpoint_interval. I'm guessing that's the issue!

It looks like you may be missing the underscore in `encryption_passphrase`? Same for `checkpoint_interval`. I'm guessing that's the issue!

It looks like you may be missing the underscore in encryption_passphrase? Same for checkpoint_interval. I'm guessing that's the issue!

Nope, the screenshot had taken from "nano" editor thats why it is not showing up.
image

> It looks like you may be missing the underscore in `encryption_passphrase`? Same for `checkpoint_interval`. I'm guessing that's the issue! Nope, the screenshot had taken from "nano" editor thats why it is not showing up. ![image](/attachments/f4bf81a2-9fbe-4adf-93f0-989d6bab1dff)
Owner

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!

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!

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

> 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](https://mega.nz/file/EdhzSAJA#5TRWlrfgT1pTfmeiC1DFxJRw9axmsKpfw-vw4eqYX3I)
Owner

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 the storage section. (The fix is to remove the # before storage:.)
  • hooks: is commented out even though there are options configured in the hooks section.
  • You have several hook values configured (e.g. - echo "Starting a backup." but the corresponding hook keys are commented out. For instance before_backup:, before_prune:, and so on are commented out, even though they shouldn't be when a value is present.

Hope that helps!

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 the `storage` section. (The fix is to remove the `# ` before `storage:`.) * `hooks:` is commented out even though there are options configured in the `hooks` section. * You have several hook values configured (e.g. `- echo "Starting a backup."` but the corresponding hook keys are commented out. For instance `before_backup:`, `before_prune:`, and so on are commented out, even though they shouldn't be when a value is present. Hope that helps!
witten added the
question / support
label 8 months ago

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 the storage section. (The fix is to remove the # before storage:.)
  • hooks: is commented out even though there are options configured in the hooks section.
  • You have several hook values configured (e.g. - echo "Starting a backup." but the corresponding hook keys are commented out. For instance before_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.

Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: summary:
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: /etc/borgmatic/config.yaml: Error parsing configuration file
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: --- Logging error ---
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Traceback (most recent call last):
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 1083, in emit
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: msg = self.format(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 927, in format
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return fmt.format(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/logger.py", line 100, in format
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return color_text(color, record.msg)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/logger.py", line 110, in color_text
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return '{}{}{}'.format(color, message, colorama.Style.RESET_ALL)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in str
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 32, in format_error
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: if not error.path:
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: AttributeError: 'str' object has no attribute 'path'
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Call stack:
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/bin/borgmatic", line 33, in
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: sys.exit(load_entry_point('borgmatic==1.5.20', 'console_scripts', 'borgmatic')())
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/commands/borgmatic.py", line 815, in main
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: logger.handle(log)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 1599, in handle
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: self.callHandlers(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 1661, in callHandlers
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: hdlr.handle(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 952, in handle
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: self.emit(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/logger.py", line 73, in emit
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: self.log_level_to_handler[record.levelno].emit(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Message: Validation_error('/etc/borgmatic/config.yaml', ('while parsing a block mapping\n in "/etc/borgmatic/config.yaml", line 5, column 1\ndid not find expected key\n in "/etc/borgmatic/config.yaml", line 127, column 3',))
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Arguments: ()
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: --- Logging error ---
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Traceback (most recent call last):
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/handlers.py", line 938, in emit
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: msg = self.format(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 927, in format
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return fmt.format(record)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 663, in format
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: record.message = record.getMessage()
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/init.py", line 365, in getMessage
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: msg = str(self.msg)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in str
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 32, in format_error
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: if not error.path:
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: AttributeError: 'str' object has no attribute 'path'
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Call stack:
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/bin/borgmatic", line 33, in
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: sys.exit(load_entry_point('borgmatic==1.5.20', 'console_scripts', 'borgmatic')())
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/commands/borgmatic.py", line 815, in main
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: logger.handle(log)
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Message: Validation_error('/etc/borgmatic/config.yaml', ('while parsing a block mapping\n in "/etc/borgmatic/config.yaml", line 5, column 1\ndid not find expected key\n in "/etc/borgmatic/config.yaml", line 127, column 3',))
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Arguments: ()
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL summary:
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Need some help? https://torsion.org/borgmatic/#issues
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL /etc/borgmatic/config.yaml: Error parsing configuration file
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL
Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL Need some help? https://torsion.org/borgmatic/#issues
Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865931]: /usr/bin/borgmatic failed with exit status 1.
Dec 17 07:51:41 Nextcloud-Server systemd[1]: borgmatic.service: Main process exited, code=exited, status=1/FAILURE
Dec 17 07:51:41 Nextcloud-Server systemd[1]: borgmatic.service: Failed with result 'exit-code'.
Dec 17 07:51:41 Nextcloud-Server systemd[1]: Failed to start borgmatic backup.

> 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 the `storage` section. (The fix is to remove the `# ` before `storage:`.) > * `hooks:` is commented out even though there are options configured in the `hooks` section. > * You have several hook values configured (e.g. `- echo "Starting a backup."` but the corresponding hook keys are commented out. For instance `before_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. > Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: summary: Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: /etc/borgmatic/config.yaml: Error parsing configuration file Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: --- Logging error --- Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Traceback (most recent call last): Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 1083, in emit Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: msg = self.format(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 927, in format Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return fmt.format(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/logger.py", line 100, in format Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return color_text(color, record.msg) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/logger.py", line 110, in color_text Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return '{}{}{}'.format(color, message, colorama.Style.RESET_ALL) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in __str__ Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in <genexpr> Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 32, in format_error Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: if not error.path: Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: AttributeError: 'str' object has no attribute 'path' Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Call stack: Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/bin/borgmatic", line 33, in <module> Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: sys.exit(load_entry_point('borgmatic==1.5.20', 'console_scripts', 'borgmatic')()) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/commands/borgmatic.py", line 815, in main Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: logger.handle(log) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 1599, in handle Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: self.callHandlers(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 1661, in callHandlers Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: hdlr.handle(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 952, in handle Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: self.emit(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/logger.py", line 73, in emit Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: self.log_level_to_handler[record.levelno].emit(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Message: Validation_error('/etc/borgmatic/config.yaml', ('while parsing a block mapping\n in "/etc/borgmatic/config.yaml", line 5, column 1\ndid not find expected key\n in "/etc/borgmatic/config.yaml", line 127, column 3',)) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Arguments: () Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: --- Logging error --- Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Traceback (most recent call last): Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/handlers.py", line 938, in emit Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: msg = self.format(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 927, in format Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: return fmt.format(record) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 663, in format Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: record.message = record.getMessage() Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib64/python3.9/logging/__init__.py", line 365, in getMessage Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: msg = str(self.msg) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in __str__ Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 59, in <genexpr> Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: ) + '\n'.join(format_error(error) for error in self.errors) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/config/validate.py", line 32, in format_error Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: if not error.path: Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: AttributeError: 'str' object has no attribute 'path' Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Call stack: Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/bin/borgmatic", line 33, in <module> Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: sys.exit(load_entry_point('borgmatic==1.5.20', 'console_scripts', 'borgmatic')()) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: File "/usr/lib/python3.9/site-packages/borgmatic/commands/borgmatic.py", line 815, in main Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: logger.handle(log) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Message: Validation_error('/etc/borgmatic/config.yaml', ('while parsing a block mapping\n in "/etc/borgmatic/config.yaml", line 5, column 1\ndid not find expected key\n in "/etc/borgmatic/config.yaml", line 127, column 3',)) Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Arguments: () Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL summary: Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865932]: Need some help? https://torsion.org/borgmatic/#issues Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL /etc/borgmatic/config.yaml: Error parsing configuration file Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL /etc/borgmatic/config.yaml /etc/borgmatic.d $HOME/.config/borgmatic/config.yaml $HOME/.config/borgmatic.d: No valid configuration files found Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL Dec 17 07:51:41 Nextcloud-Server borgmatic[865932]: CRITICAL Need some help? https://torsion.org/borgmatic/#issues Dec 17 07:51:41 Nextcloud-Server systemd-inhibit[865931]: /usr/bin/borgmatic failed with exit status 1. Dec 17 07:51:41 Nextcloud-Server systemd[1]: borgmatic.service: Main process exited, code=exited, status=1/FAILURE Dec 17 07:51:41 Nextcloud-Server systemd[1]: borgmatic.service: Failed with result 'exit-code'. Dec 17 07:51:41 Nextcloud-Server systemd[1]: Failed to start borgmatic backup.
Owner

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.

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.

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

> 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
Owner

It indeed looks like a spacing issue. Both the storage: and the hooks: section keys should not have any spaces right before them. I believe if you make those changes, the problem will be fixed!

It indeed looks like a spacing issue. Both the `storage:` and the `hooks:` section keys should not have any spaces right before them. I believe if you make those changes, the problem will be fixed!

It indeed looks like a spacing issue. Both the storage: and the hooks: 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.

> It indeed looks like a spacing issue. Both the `storage:` and the `hooks:` 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.
elhananjair closed this issue 7 months ago
Owner

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.

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.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#480
Loading…
There is no content yet.