Get erros / Could not find the error #135

New Issue

Closed

opened 2019-01-09 08:01:59 +00:00 by beli3ver · 3 comments

beli3ver commented 2019-01-09 08:01:59 +00:00

Copy Link

Hello,

I create a config for me. Then I modified some vars.
Now I get these errors:

validation.invalid
 --- All found errors ---
["Key 'checkpoint_interval' was not defined. Path: '/location'", "Key 'compression' was not defined. Path: '/location'", "Key 'encryption_passphrase' was not defined. Path: '/location'"]
Errors found but will not raise exception...
/etc/borgmatic/config.yaml: Error running configuration file
An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml:
Key 'checkpoint_interval' was not defined. Path: '/location'
Key 'compression' was not defined. Path: '/location'
Key 'encryption_passphrase' was not defined. Path: '/location'

This is my config file

location:
    source_directories:
        - /home

    repositories:
        - /media/malte/088360be-4d5a-4ec1-ad42-2e37227b5a5d/Sicherung
    
    encryption_passphrase: "xxxxxxxxx"

    checkpoint_interval: 1800

    compression: lz4

    exclude_patterns:
        - /home/*/.cache

retention:
    # Retention policy for how many backups to keep in each category.
    keep_daily: 7
    keep_weekly: 4
    keep_monthly: 6

consistency:
    # List of consistency checks to run: "repository", "archives", or both.
    checks:
        - repository
        - archives

Thanks for your help

Hello, I create a config for me. Then I modified some vars. Now I get these errors: ```bash validation.invalid --- All found errors --- ["Key 'checkpoint_interval' was not defined. Path: '/location'", "Key 'compression' was not defined. Path: '/location'", "Key 'encryption_passphrase' was not defined. Path: '/location'"] Errors found but will not raise exception... /etc/borgmatic/config.yaml: Error running configuration file An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml: Key 'checkpoint_interval' was not defined. Path: '/location' Key 'compression' was not defined. Path: '/location' Key 'encryption_passphrase' was not defined. Path: '/location' ``` This is my config file ```yaml location: source_directories: - /home repositories: - /media/malte/088360be-4d5a-4ec1-ad42-2e37227b5a5d/Sicherung encryption_passphrase: "xxxxxxxxx" checkpoint_interval: 1800 compression: lz4 exclude_patterns: - /home/*/.cache retention: # Retention policy for how many backups to keep in each category. keep_daily: 7 keep_weekly: 4 keep_monthly: 6 consistency: # List of consistency checks to run: "repository", "archives", or both. checks: - repository - archives ``` Thanks for your help

witten commented 2019-01-09 21:56:47 +00:00

Owner

Copy Link

It looks like you're missing the storage: section header. Judging by your config file, it should probably go above encryption_passphrase. The storage: header should have the same indent level as the existing location: header.

Give that a shot and let me know if it works out for you!

It looks like you're missing the `storage:` section header. Judging by your config file, it should probably go above `encryption_passphrase`. The `storage:` header should have the same indent level as the existing `location:` header. Give that a shot and let me know if it works out for you!

witten added the

question / support

label 2019-01-09 21:56:54 +00:00

witten commented 2019-01-09 21:58:09 +00:00

Owner

Copy Link

Oh, and exclude_patterns needs to go in the location: section, so that'll have to be moved. You can check out the original config file schema here for reference: https://projects.torsion.org/witten/borgmatic/src/branch/master/borgmatic/config/schema.yaml

Oh, and `exclude_patterns` needs to go in the `location:` section, so that'll have to be moved. You can check out the original config file schema here for reference: https://projects.torsion.org/witten/borgmatic/src/branch/master/borgmatic/config/schema.yaml

witten commented 2019-02-09 23:48:25 +00:00

Owner

Copy Link

Hopefully that works out for you. If not, please feel free to comment or file another issue!

Hopefully that works out for you. If not, please feel free to comment or file another issue!

witten closed this issue 2019-02-09 23:48:25 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

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#135

No description provided.