Can't invoke scripts before/after #199

New Issue

Closed

opened 2019-06-30 23:40:42 +00:00 by thisfro · 3 comments

thisfro commented 2019-06-30 23:40:42 +00:00

Copy Link

What I'm trying to do and why

Run a script before and after the actual backup process

Steps to reproduce (if a bug)

/etc/borgmatic.d/nextcloud.yaml has those lines:

hooks:
    before_backup:
        - sudo -u www-data php /var/www/cloud/occ maintenance:mode --on
        - /opt/borg-scripts/bkp_nextcloud.sh

    after_backup:
        - sudo -u www-data php /var/www/cloud/occ maintenance:mode --off

then I run sudo borgmatic --verbosity 2 -c /etc/borgmatic.d/nextcloud.yaml

Actual behavior (if a bug)

summary:  
/etc/borgmatic.d/nextcloud.yaml: Error parsing configuration file. 
An error occurred while parsing a configuration file at /etc/borgmatic.d/nextcloud.yaml:  
while scanning for the next token 
found character that cannot start any token 
  in "/etc/borgmatic.d/nextcloud.yaml", line 197, column 1

Expected behavior (if a bug)

Run the command

Other notes / implementation ideas

Line 197 is the first before command.
I also tried the "standard" command (echo "Starting a backup job.") in the yaml config, same result
Am I missing something or is this a bug (can't be the first one)?

Environment

borgmatic version: [1.3.12]

borgmatic installation method: pip

Borg version: 1.1.9

Python version: 3.5.2

operating system and version: Ubuntu 16.04, 4.15.0-52-generic

#### What I'm trying to do and why Run a script before and after the actual backup process #### Steps to reproduce (if a bug) `/etc/borgmatic.d/nextcloud.yaml` has those lines: ``` hooks: before_backup: - sudo -u www-data php /var/www/cloud/occ maintenance:mode --on - /opt/borg-scripts/bkp_nextcloud.sh after_backup: - sudo -u www-data php /var/www/cloud/occ maintenance:mode --off ``` then I run `sudo borgmatic --verbosity 2 -c /etc/borgmatic.d/nextcloud.yaml` #### Actual behavior (if a bug) ``` summary: /etc/borgmatic.d/nextcloud.yaml: Error parsing configuration file. An error occurred while parsing a configuration file at /etc/borgmatic.d/nextcloud.yaml: while scanning for the next token found character that cannot start any token in "/etc/borgmatic.d/nextcloud.yaml", line 197, column 1 ``` #### Expected behavior (if a bug) Run the command #### Other notes / implementation ideas Line 197 is the first before command. I also tried the "standard" command (`echo "Starting a backup job."`) in the yaml config, same result Am I missing something or is this a bug (can't be the first one)? #### Environment **borgmatic version:** [1.3.12] **borgmatic installation method:** pip **Borg version:** 1.1.9 **Python version:** 3.5.2 **operating system and version:** Ubuntu 16.04, 4.15.0-52-generic

thisfro closed this issue 2019-06-30 23:40:52 +00:00

thisfro reopened this issue 2019-06-30 23:40:55 +00:00

witten commented 2019-06-30 23:49:04 +00:00

Owner

Copy Link

Thank you for reporting this! I managed to get a reproduction of the same error message by using tabs to indent the hook command lines instead of spaces. If you indeed have tabs there, could you try replacing them with the requisite number of spaces?

Thank you for reporting this! I managed to get a reproduction of the same error message by using tabs to indent the hook command lines instead of spaces. If you indeed have tabs there, could you try replacing them with the requisite number of spaces?

witten added the

question / support

label 2019-06-30 23:50:07 +00:00

witten referenced this issue from a commit 2019-06-30 23:58:58 +00:00

Add note to documentation about using spaces instead of tabs for indentation, as YAML does not allow tabs (#199).

thisfro commented 2019-07-01 00:01:05 +00:00

Author

Copy Link

Yes that's absolutely the case! Didn't even realize... Thx alot!

Yes that's absolutely the case! Didn't even realize... Thx alot!

thisfro closed this issue 2019-07-01 00:01:05 +00:00

witten commented 2019-07-01 00:01:53 +00:00

Owner

Copy Link

Glad that was it! I'm adding info about this to the documentation, as it's not at all obvious from the error message. Thanks again for filing.

Glad that was it! I'm adding info about this to the documentation, as it's not at all obvious from the error message. Thanks again for filing.

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

No description provided.