borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 53 Pull Requests 2 Actions Packages Releases 121 Activity

Is borg debug supported as arbitrary borg command? #538

New Issue
Closed
opened 2022-05-29 13:32:16 +00:00 by ams_tschoening · 2 comments
ams_tschoening commented 2022-05-29 13:32:16 +00:00
Copy Link

What I'm trying to do and why

For the last too weeks I've multiple times ran into an issue with corrupted repo indexes and wanted to debug further using e.g. the following commands:

sudo borgmatic --config ~/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml --verbosity 2 borg debug get-obj 28eac01d646f253f847681d6e46f342d53873c905c6eb839ff3181e84232e4f5

sudo borgmatic --config ~/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml --verbosity 2 borg debug info

Actual behavior (if a bug)

Though, it seems that BorgMatic generates a wrong command line for those commands:

Ensuring legacy configuration is upgraded
borg --version --debug --show-rc
amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Running arbitrary Borg command
borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft get-obj 28eac01d646f253f847681d6e46f342d53873c905c6eb839ff3181e84232e4f5 --debug --show-rc
usage: borg debug [-h] [--critical] [--error] [--warning] [--info] [--debug]
                  [--debug-topic TOPIC] [-p] [--log-json]
                  [--lock-wait SECONDS] [--bypass-lock] [--show-version]
                  [--show-rc] [--umask M] [--remote-path PATH]
                  [--remote-ratelimit RATE] [--consider-part-files]
                  [--debug-profile FILE] [--rsh RSH]
                  <command> ...
borg debug: error: argument <command>: invalid choice: 'amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft' (choose from 'info', 'dump-archive-items', 'dump-archive', 'dump-manifest', 'dump-repo-objs', 'search-repo-objs', 'get-obj', 'put-obj', 'delete-obj', 'refcount-obj', 'dump-hints', 'convert-profile')
amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Error running actions for repository
Command 'borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft get-obj 28eac01d646f253f847681d6e46f342d53873c905c6eb839ff3181e84232e4f5 --debug --show-rc' returned non-zero exit status 2.
/home/ams_d_bak_borg/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml: Error running configuration file

Ensuring legacy configuration is upgraded
borg --version --debug --show-rc
amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Running arbitrary Borg command
borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft info --debug --show-rc
usage: borg debug [-h] [--critical] [--error] [--warning] [--info] [--debug]
                  [--debug-topic TOPIC] [-p] [--log-json]
amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Error running actions for repository
Command 'borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft info --debug --show-rc' returned non-zero exit status 2.
/home/ams_d_bak_borg/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml: Error running configuration file

It seems that the path to the repo is wronlgy put where the command of debug is expected instead.

Expected behavior (if a bug)

borg debug info|get-obj|... to succeed.

Other notes / implementation ideas

Environment

borgmatic version: 1.5.24
borgmatic installation method: PIP, system wide
Borg version: 1.1.16
Python version: 3.8.10
operating system and version: Ubuntu 20.04

#### What I'm trying to do and why For the last too weeks I've multiple times ran into an issue with [corrupted repo indexes](https://github.com/borgbackup/borg/issues/6687) and wanted to debug further using e.g. the following commands: ```bash sudo borgmatic --config ~/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml --verbosity 2 borg debug get-obj 28eac01d646f253f847681d6e46f342d53873c905c6eb839ff3181e84232e4f5 ``` ```bash sudo borgmatic --config ~/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml --verbosity 2 borg debug info ``` #### Actual behavior (if a bug) Though, it seems that BorgMatic generates a wrong command line for those commands: ```bash Ensuring legacy configuration is upgraded borg --version --debug --show-rc amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Running arbitrary Borg command borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft get-obj 28eac01d646f253f847681d6e46f342d53873c905c6eb839ff3181e84232e4f5 --debug --show-rc usage: borg debug [-h] [--critical] [--error] [--warning] [--info] [--debug] [--debug-topic TOPIC] [-p] [--log-json] [--lock-wait SECONDS] [--bypass-lock] [--show-version] [--show-rc] [--umask M] [--remote-path PATH] [--remote-ratelimit RATE] [--consider-part-files] [--debug-profile FILE] [--rsh RSH] <command> ... borg debug: error: argument <command>: invalid choice: 'amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft' (choose from 'info', 'dump-archive-items', 'dump-archive', 'dump-manifest', 'dump-repo-objs', 'search-repo-objs', 'get-obj', 'put-obj', 'delete-obj', 'refcount-obj', 'dump-hints', 'convert-profile') amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Error running actions for repository Command 'borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft get-obj 28eac01d646f253f847681d6e46f342d53873c905c6eb839ff3181e84232e4f5 --debug --show-rc' returned non-zero exit status 2. /home/ams_d_bak_borg/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml: Error running configuration file ``` ```bash Ensuring legacy configuration is upgraded borg --version --debug --show-rc amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Running arbitrary Borg command borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft info --debug --show-rc usage: borg debug [-h] [--critical] [--error] [--warning] [--info] [--debug] [--debug-topic TOPIC] [-p] [--log-json] amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft: Error running actions for repository Command 'borg debug amsoft-sbox.bitstore.group:bak_borg/hosts/group.bitstore.amsoft info --debug --show-rc' returned non-zero exit status 2. /home/ams_d_bak_borg/.config/borgmatic.d/hosts/bts.ams/net.elrev.software.yaml: Error running configuration file ``` It seems that the path to the repo is wronlgy put where the command of `debug` is expected instead. #### Expected behavior (if a bug) `borg debug info|get-obj|...` to succeed. #### Other notes / implementation ideas #### Environment **borgmatic version:** 1.5.24 **borgmatic installation method:** PIP, system wide **Borg version:** 1.1.16 **Python version:** 3.8.10 **operating system and version:** Ubuntu 20.04
witten commented 2022-05-29 22:44:31 +00:00
Owner
Copy Link

This is implemented in master now, and will be part of the next release. Thanks for suggesting this!

This is implemented in master now, and will be part of the next release. Thanks for suggesting this!
👍 1
witten commented 2022-05-31 16:45:15 +00:00
Owner
Copy Link

This has been released in borgmatic 1.6.2!

This has been released in borgmatic 1.6.2!
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
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#538
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?