/etc/borgmatic/config.yaml: Configuration sections (like location: and storage:) are deprecated #744

New Issue

Closed

opened 2023-08-15 20:59:58 +00:00 by phamhung77 · 5 comments

phamhung77 commented 2023-08-15 20:59:58 +00:00

Copy Link

What I'm trying to do and why

Running backup with Borgmatic 1.8. The config is 1.7 format, and I am trying to convert to 1.8 format

Steps to reproduce

Updating the config.yaml format

1. Old format:
   location:
   source_directories:

   • /home

2. New format:
   source_directories:

   • /home

Actual behavior

/etc/borgmatic/config.yaml: Error parsing configuration file
An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml:
while parsing a block mapping
in "", line 12, column 1

/*** line 12, column 1 is the new "source_directories:" line ***/

Expected behavior

No response

Other notes / implementation ideas

No response

borgmatic version

1.8.0

borgmatic installation method

DNF on CloudLinux 9

Borg version

1.2.4

Python version

3.9.16

Database version (if applicable)

No response

Operating system and version

CloudLinux 9.2

### What I'm trying to do and why Running backup with Borgmatic 1.8. The config is 1.7 format, and I am trying to convert to 1.8 format ### Steps to reproduce Updating the config.yaml format 1. Old format: location: source_directories: - /home 2. New format: source_directories: - /home ### Actual behavior /etc/borgmatic/config.yaml: Error parsing configuration file An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml: while parsing a block mapping in "<unicode string>", line 12, column 1 _/*** line 12, column 1 is the new "source_directories:" line ***/_ ### Expected behavior _No response_ ### Other notes / implementation ideas _No response_ ### borgmatic version 1.8.0 ### borgmatic installation method DNF on CloudLinux 9 ### Borg version 1.2.4 ### Python version 3.9.16 ### Database version (if applicable) _No response_ ### Operating system and version CloudLinux 9.2

witten commented 2023-08-15 21:54:59 +00:00

Owner

Copy Link

I'm not sure exactly what's going on with parsing your configuration file, but I imagine there's some problem with its formatting. Would you be able to attach your exact configuration file (with any sensitive information redacted) so that I can take a look at it and try to reproduce the problem locally? Alternatively, you can link to your config on a gist or pastebin service if you'd prefer. Thank you!

I'm not sure exactly what's going on with parsing your configuration file, but I imagine there's some problem with its formatting. Would you be able to attach your exact configuration file (with any sensitive information redacted) so that I can take a look at it and try to reproduce the problem locally? Alternatively, you can link to your config on a gist or pastebin service if you'd prefer. Thank you!

witten added the

question / support

label 2023-08-15 21:55:18 +00:00

phamhung77 commented 2023-08-16 06:26:01 +00:00

Author

Copy Link

I attached the config file. The errors are:

borgmatic --verbosity 2

/etc/borgmatic/config.yaml /etc/borgmatic.d /root/.config/borgmatic/config.yaml /root/.config/borgmatic.d: No valid configuration files found

summary:
/etc/borgmatic/config.yaml: Loading configuration file
/etc/borgmatic/config.yaml: Error parsing configuration file
An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml:
while parsing a block mapping
in "", line 1, column 1
did not find expected key
in "", line 11, column 2
/etc/borgmatic/config.yaml /etc/borgmatic.d /root/.config/borgmatic/config.yaml /root/.config/borgmatic.d: No valid configuration files found

Need some help? https://torsion.org/borgmatic/#issues

I attached the config file. The errors are: # borgmatic --verbosity 2 /etc/borgmatic/config.yaml /etc/borgmatic.d /root/.config/borgmatic/config.yaml /root/.config/borgmatic.d: No valid configuration files found summary: /etc/borgmatic/config.yaml: Loading configuration file /etc/borgmatic/config.yaml: Error parsing configuration file An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml: while parsing a block mapping in "<unicode string>", line 1, column 1 did not find expected key in "<unicode string>", line 11, column 2 /etc/borgmatic/config.yaml /etc/borgmatic.d /root/.config/borgmatic/config.yaml /root/.config/borgmatic.d: No valid configuration files found Need some help? https://torsion.org/borgmatic/#issues

config-yaml.txt

474 B

witten commented 2023-08-16 15:51:49 +00:00

Owner

Copy Link

The error message you're getting sure isn't helping, but I think the problem is that some of your options are not fully left-aligned in your configuration file. In other words, options like one_file_system and exclude_caches (and all the following options) have extra spaces before them that should be removed. Once you remove those spaces and the options are properly lined up, I'm pretty sure your configuration file will work! Let me know if that does it for you.

The error message you're getting sure isn't helping, but I think the problem is that some of your options are not fully left-aligned in your configuration file. In other words, options like `one_file_system` and `exclude_caches` (and all the following options) have extra spaces before them that should be removed. Once you remove those spaces and the options are properly lined up, I'm pretty sure your configuration file will work! Let me know if that does it for you.

phamhung77 commented 2023-08-16 18:43:21 +00:00

Author

Copy Link

Thank you. It works when I deleted all spaces before each line.

Thank you. It works when I deleted all spaces before each line.

witten commented 2023-08-16 19:18:45 +00:00

Owner

Copy Link

Awesome, glad to hear it! Feel free to file another ticket if you encounter any other problems.

Awesome, glad to hear it! Feel free to file another ticket if you encounter any other problems.

witten closed this issue 2023-08-16 19:18:45 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#744

No description provided.