Disabling Checks is broken: {'name': 'disabled'} is not of type 'string' #639

New Issue

Closed

opened 2023-02-12 12:29:50 +00:00 by Schroedingers-Cat · 3 comments

Schroedingers-Cat commented 2023-02-12 12:29:50 +00:00

Copy Link

What I'm trying to do and why

I'm trying to disable health checks on my backup client because the storage is a read-only remote handling consistency checks on its own terms and can perform these checks faster.

Steps to reproduce (if a bug)

According to the docs, disabling consistency checks works like this:

consistency:
    checks:
        - name: disabled

So all I do is adding these lines to a working config under /root/.config/borgmatic.d/profile-name.yaml.

This is how the complete file looks like:

---
location:
  source_directories:
    - /path/to/source/directory
  repositories:
    - username@remotehost:/path/To-Remote-Backup/archive.borg
  one_file_system: true
storage:
  archive_name_format: "{hostname}-Profile-Name-{now}"
retention:
    prefix: "{hostname}"
consistency:
    checks:
        - name: disabled

After that, just run a simple borgmatic list --verbosity 2.

Actual behavior (if a bug)

This is what I'm getting:

Ensuring legacy configuration is upgraded
/etc/borgmatic/config.yaml /etc/borgmatic.d /root/.config/borgmatic/config.yaml /root/.config/borgmatic.d: No valid configuration files found

summary:
/root/.config/borgmatic.d/profile-name.yaml: Error parsing configuration file
An error occurred while parsing a configuration file at /root/.config/borgmatic.d/profile-name.yaml:
At 'consistency.checks[0]': {'name': 'disabled'} is not of type 'string'
At 'consistency.checks[0]': {'name': 'disabled'} is not one of ['repository', 'archives', 'data', 'extract', 'disabled']
/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

Expected behavior (if a bug)

The expected behavior would be that the example from the documentation worked.

Other notes / implementation ideas

I tried some variants of the given config above because of the type not being 'string' like - name: 'disabled', - name: "disabled" or - name: repository but none of them changed the error message.

Environment

borgmatic version: 1.5.20

borgmatic installation method: Ubuntu/apt

Borg version: borg 1.2.3

Python version: Python 3.10.6

operating system and version: Ubuntu Server 22.04

#### What I'm trying to do and why I'm trying to disable health checks on my backup client because the storage is a read-only remote handling consistency checks on its own terms and can perform these checks faster. #### Steps to reproduce (if a bug) According to the [docs](https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#disabling-checks), disabling consistency checks works like this: ```yaml consistency: checks: - name: disabled ``` So all I do is adding these lines to a working config under `/root/.config/borgmatic.d/profile-name.yaml`. This is how the complete file looks like: ```yaml --- location: source_directories: - /path/to/source/directory repositories: - username@remotehost:/path/To-Remote-Backup/archive.borg one_file_system: true storage: archive_name_format: "{hostname}-Profile-Name-{now}" retention: prefix: "{hostname}" consistency: checks: - name: disabled ``` After that, just run a simple `borgmatic list --verbosity 2`. #### Actual behavior (if a bug) This is what I'm getting: ``` Ensuring legacy configuration is upgraded /etc/borgmatic/config.yaml /etc/borgmatic.d /root/.config/borgmatic/config.yaml /root/.config/borgmatic.d: No valid configuration files found summary: /root/.config/borgmatic.d/profile-name.yaml: Error parsing configuration file An error occurred while parsing a configuration file at /root/.config/borgmatic.d/profile-name.yaml: At 'consistency.checks[0]': {'name': 'disabled'} is not of type 'string' At 'consistency.checks[0]': {'name': 'disabled'} is not one of ['repository', 'archives', 'data', 'extract', 'disabled'] /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 ``` #### Expected behavior (if a bug) The expected behavior would be that the example from the documentation worked. #### Other notes / implementation ideas I tried some variants of the given config above because of the type not being 'string' like `- name: 'disabled'`, `- name: "disabled"` or ``- name: repository`` but none of them changed the error message. #### Environment **borgmatic version:** 1.5.20 **borgmatic installation method:** Ubuntu/apt **Borg version:** borg 1.2.3 **Python version:** Python 3.10.6 **operating system and version:** Ubuntu Server 22.04

Schroedingers-Cat changed title from Disabling Checks is broken / {'name': 'disabled'} is not of type 'string' to Disabling Checks is broken: {'name': 'disabled'} is not of type 'string' 2023-02-12 12:31:22 +00:00

witten commented 2023-02-13 05:31:35 +00:00

Owner

Copy Link

Looks like this is a version mismatch. To disable checks in the version of borgmatic you're using, try this:

consistency:
    checks:
        - disabled

Or better yet, upgrade borgmatic if possible. (The version you're using is almost a year and a half old.)

I'll clarify this detail in the documentation. Thanks for reporting it!

Looks like this is a version mismatch. To disable checks in the version of borgmatic you're using, try this: ``` consistency: checks: - disabled ``` Or better yet, upgrade borgmatic if possible. (The version you're using is almost a year and a half old.) I'll clarify this detail in the documentation. Thanks for reporting it!

witten added the

question / support

label 2023-02-13 05:31:42 +00:00

witten referenced this issue from a commit 2023-02-13 05:43:20 +00:00

Clarify "checks" configuration documentation for older versions of borgmatic (#639).

Schroedingers-Cat commented 2023-02-13 11:12:29 +00:00

Author

Copy Link

You're right. Using your example works just fine. Thanks a lot for your help!

Or better yet, upgrade borgmatic if possible. (The version you're using is almost a year and a half old.)

In case someone else wants to install the latest borgmatic version on Ubuntu Server 22.04 but wants to avoid using other package managers than apt, I've found this PPA: https://launchpad.net/~vincent-c/+archive/ubuntu/ppa/+packages

I just downloaded the current borgmatic deb file and installed it via dpkg on top of the existing one. Meaning, should my apt sources ever get a newer version for borgmatic, it'll be installed automatically.

You're right. Using your example works just fine. Thanks a lot for your help! > Or better yet, upgrade borgmatic if possible. (The version you're using is almost a year and a half old.) In case someone else wants to install the latest borgmatic version on Ubuntu Server 22.04 but wants to avoid using other package managers than apt, I've found this PPA: https://launchpad.net/~vincent-c/+archive/ubuntu/ppa/+packages I just downloaded the current borgmatic deb file and installed it via dpkg on top of the existing one. Meaning, should my apt sources ever get a newer version for borgmatic, it'll be installed automatically.

witten commented 2023-02-13 22:59:48 +00:00

Owner

Copy Link

Awesome, glad to here you've got it working! The documentation has been updated as well.

Awesome, glad to here you've got it working! The documentation has been updated as well.

witten closed this issue 2023-02-13 22:59:48 +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#639

No description provided.