borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
14
57
Fork 41
Code Issues 54 Pull Requests 2 Actions Packages Releases 122 Activity

config file validation fails #698

New Issue
Closed
opened 2023-05-14 12:05:44 +00:00 by Marcs1974 · 6 comments
Marcs1974 commented 2023-05-14 12:05:44 +00:00
Copy Link

What I'm trying to do and why

Setup initial config file

Steps to reproduce (if a bug)

# Where to look for files to backup, and where to store those backups.
# See https://borgbackup.readthedocs.io/en/stable/quickstart.html and
# https://borgbackup.readthedocs.io/en/stable/usage/create.html
# for details.
location:
    # List of source directories to backup. Globs and tildes are
    # expanded. Do not backslash spaces in path names.
    source_directories:
        - /srv/mergerfs/JGPool/LIVE

    # Paths to local or remote repositories (required). Tildes are
    # expanded. Multiple repositories are backed up to in
    # sequence. Borg placeholders can be used. See the output of
    # "borg help placeholders" for details. See ssh_command for
    # SSH options like identity file or port. If systemd service
    # is used, then add local repository paths in the systemd
    # service file to the ReadWritePaths list.
    repositories:
        - path: /srv/mergerfs/JGPool/BorgRepo
          label: borgbase

Actual behavior (if a bug)

validate-borgmatic-config
/etc/borgmatic/config.yaml: Error parsing configuration file
An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml:
At 'location': Additional properties are not allowed ('archive_name_format' was unexpected)
At 'location.repositories[0]': {'path': '/srv/mergerfs/JGPool/BorgRepo', 'label': 'borgbase'} is not of type 'string'

Expected behavior (if a bug)

verify config file

Other notes / implementation ideas

borgmatic version: [version here]
1.7.4

borgmatic installation method: [e.g., Debian package, Docker container, etc.]
Debian
Borg version: [version here]
1.2.3.

#### What I'm trying to do and why Setup initial config file #### Steps to reproduce (if a bug) ``` # Where to look for files to backup, and where to store those backups. # See https://borgbackup.readthedocs.io/en/stable/quickstart.html and # https://borgbackup.readthedocs.io/en/stable/usage/create.html # for details. location: # List of source directories to backup. Globs and tildes are # expanded. Do not backslash spaces in path names. source_directories: - /srv/mergerfs/JGPool/LIVE # Paths to local or remote repositories (required). Tildes are # expanded. Multiple repositories are backed up to in # sequence. Borg placeholders can be used. See the output of # "borg help placeholders" for details. See ssh_command for # SSH options like identity file or port. If systemd service # is used, then add local repository paths in the systemd # service file to the ReadWritePaths list. repositories: - path: /srv/mergerfs/JGPool/BorgRepo label: borgbase ``` #### Actual behavior (if a bug) validate-borgmatic-config /etc/borgmatic/config.yaml: Error parsing configuration file An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml: At 'location': Additional properties are not allowed ('archive_name_format' was unexpected) At 'location.repositories[0]': {'path': '/srv/mergerfs/JGPool/BorgRepo', 'label': 'borgbase'} is not of type 'string' #### Expected behavior (if a bug) verify config file #### Other notes / implementation ideas **borgmatic version:** [version here] 1.7.4 **borgmatic installation method:** [e.g., Debian package, Docker container, etc.] Debian **Borg version:** [version here] 1.2.3.
diivi commented 2023-05-14 12:26:15 +00:00
Collaborator
Copy Link

One of the errors that says

At 'location.repositories[0]': {'path': '/srv/mergerfs/JGPool/BorgRepo', 'label': 'borgbase'} is not of type 'string'

is because of your Borgmatic version.

Labels for repos were introduced in version 1.7.10 (ref: https://projects.torsion.org/borgmatic-collective/borgmatic/src/branch/main/NEWS).

For earlier versions it used to be just a list of repo urls.

One of the errors that says ``` At 'location.repositories[0]': {'path': '/srv/mergerfs/JGPool/BorgRepo', 'label': 'borgbase'} is not of type 'string' ``` is because of your Borgmatic version. Labels for repos were introduced in version 1.7.10 (ref: https://projects.torsion.org/borgmatic-collective/borgmatic/src/branch/main/NEWS). For earlier versions it used to be just a list of repo urls.
Marcs1974 commented 2023-05-14 12:49:57 +00:00
Author
Copy Link

OK. thanks.
I removed the label and removed the 'path:' signifier to accomodate the old version. Same problem, different error message:

# Where to look for files to backup, and where to store those backups.
# See https://borgbackup.readthedocs.io/en/stable/quickstart.html and
# https://borgbackup.readthedocs.io/en/stable/usage/create.html
# for details.
location:
    # List of source directories to backup. Globs and tildes are
    # expanded. Do not backslash spaces in path names.
    source_directories:
        - /srv/mergerfs/JGPool/LIVE

    # Paths to local or remote repositories (required). Tildes are
    # expanded. Multiple repositories are backed up to in
    # sequence. Borg placeholders can be used. See the output of
    # "borg help placeholders" for details. See ssh_command for
    # SSH options like identity file or port. If systemd service
    # is used, then add local repository paths in the systemd
    # service file to the ReadWritePaths list.
    repositories:
        - /srv/mergerfs/JGPool/BorgRepo
#          label: borgbase
        #- ssh://user@backupserver/./sourcehostname.borg
        #- ssh://user@backupserver/./{fqdn}
#        - /srv/remotemount/NNnfs2_T17/BorgFrom180
#         label: T17_backup

root@raspberrypi:/etc/borgmatic# validate-borgmatic-config
/etc/borgmatic/config.yaml: Error parsing configuration file
An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml:
At 'location': Additional properties are not allowed ('archive_name_format' was unexpected)

OK. thanks. I removed the label and removed the 'path:' signifier to accomodate the old version. Same problem, different error message: ``` # Where to look for files to backup, and where to store those backups. # See https://borgbackup.readthedocs.io/en/stable/quickstart.html and # https://borgbackup.readthedocs.io/en/stable/usage/create.html # for details. location: # List of source directories to backup. Globs and tildes are # expanded. Do not backslash spaces in path names. source_directories: - /srv/mergerfs/JGPool/LIVE # Paths to local or remote repositories (required). Tildes are # expanded. Multiple repositories are backed up to in # sequence. Borg placeholders can be used. See the output of # "borg help placeholders" for details. See ssh_command for # SSH options like identity file or port. If systemd service # is used, then add local repository paths in the systemd # service file to the ReadWritePaths list. repositories: - /srv/mergerfs/JGPool/BorgRepo # label: borgbase #- ssh://user@backupserver/./sourcehostname.borg #- ssh://user@backupserver/./{fqdn} # - /srv/remotemount/NNnfs2_T17/BorgFrom180 # label: T17_backup ``` root@raspberrypi:/etc/borgmatic# validate-borgmatic-config /etc/borgmatic/config.yaml: Error parsing configuration file An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml: At 'location': Additional properties are not allowed ('archive_name_format' was unexpected)
diivi commented 2023-05-14 13:02:19 +00:00
Collaborator
Copy Link

Can you share your complete config? Looks like 'archive_name_format' is uncommented while it's parent key (storage) is commented.

Can you share your complete config? Looks like 'archive_name_format' is uncommented while it's parent key (storage) is commented.
Marcs1974 commented 2023-05-14 13:10:57 +00:00
Author
Copy Link

I found my error.
Further down in the file I was defining archive-name but had 'storage:' commented out. My bad.

I found my error. Further down in the file I was defining archive-name but had 'storage:' commented out. My bad.
👍 1
Marcs1974 commented 2023-05-14 13:11:55 +00:00
Author
Copy Link

thanks for your help.
If I may recommend one feature then remove the hierarchical structure in the config file.
Just parameters would be much much easier to manage.
or alternativelly
keep the hierarchy and comment all top level section headers out by default, and just allow empty sections (if no parameters used)

thanks for your help. If I may recommend one feature then remove the hierarchical structure in the config file. Just parameters would be much much easier to manage. or alternativelly keep the hierarchy and comment all top level section headers out by default, and just allow empty sections (if no parameters used)
witten commented 2023-05-14 16:41:30 +00:00
Owner
Copy Link

I'm glad to hear you got it sorted out, and thanks for the recommendation. I've considered removing the section headings as you suggest, but there are other parts of the configuration file that benefit from the hierarchy. Maybe it would make sense to remove the top-level hierarchy while leaving the other parts.

I'm glad to hear you got it sorted out, and thanks for the recommendation. I've considered removing the section headings as you suggest, but there are other parts of the configuration file that benefit from the hierarchy. Maybe it would make sense to remove the top-level hierarchy while leaving the other parts.
witten added the
question / support
 label 2023-05-14 16:41:38 +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
3 Participants
Notifications
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#698
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?