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

Borgmatic runs any underlying borg command twice #386

New Issue
Closed
opened 2021-01-26 08:32:49 +00:00 by coaxial · 2 comments
coaxial commented 2021-01-26 08:32:49 +00:00
Copy Link

What I'm trying to do and why

When I run any borgmatic commands that calls borg, it runs them twice.

Steps to reproduce (if a bug)

location:
    source_directories:
        - ~/somedit
    repositories:
        - host:repo
    one_file_system: true
storage:
    encryption_passcommand: cat /passphrase
retention:
    keep_daily: 7
    keep_weekly: 4
    keep_monthly: 6
    keep_yearly: 1
consistency:
    checks:
        - repository
        - archives
    check_last: 3

Run borgmatic list for example, and see that it runs the underlying borg command twice, showing the output twice. Same goes when making a backup: it makes the backup twice. But running borgmatic --version for instance only shows the output once. Same for borg --version: runs only once.

Actual behavior (if a bug)

$ borgmatic list --verbosity 2
Ensuring legacy configuration is upgraded
host:repo: Listing archives
borg list --debug --show-rc host:repo
using builtin fallback logging configuration
35 self tests completed in 0.11 seconds
SSH command line: ['ssh', 'host', 'borg', 'serve', '--umask=077', '--debug']
Remote: using builtin fallback logging configuration
Remote: using builtin fallback logging configuration
Remote: Initialized logging system for JSON-based protocol
Remote: Resolving repository path b'repo'
Remote: Resolved repository path to '/data1/home/user/repo'
Remote: Verified integrity of /data1/home/user/repo/index.1645
TAM-verified manifest
security: read previous location 'ssh://host/./repo'
security: read manifest timestamp '2021-01-26T08:14:38.103280'
security: determined newest manifest timestamp as 2021-01-26T08:14:38.103280
security: repository checks ok, allowing access
<backups list>
RemoteRepository: 213 B bytes sent, 3.44 kB bytes received, 5 messages sent
terminating with success status, rc 0
host:repo: Listing archives
borg list --debug --show-rc host:repo
using builtin fallback logging configuration
35 self tests completed in 0.10 seconds
SSH command line: ['ssh', 'host', 'borg', 'serve', '--umask=077', '--debug']
Remote: using builtin fallback logging configuration
Remote: using builtin fallback logging configuration
Remote: Initialized logging system for JSON-based protocol
Remote: Resolving repository path b'repo'
Remote: Resolved repository path to '/data1/home/user/repo'
Remote: Verified integrity of /data1/home/host/repo/index.1645
TAM-verified manifest
security: read previous location 'ssh://host/./repo'
security: read manifest timestamp '2021-01-26T08:14:38.103280'
security: determined newest manifest timestamp as 2021-01-26T08:14:38.103280
security: repository checks ok, allowing access
<same backups list>
RemoteRepository: 213 B bytes sent, 3.45 kB bytes received, 5 messages sent
terminating with success status, rc 0

summary:
/etc/borgmatic.d/config.yaml: Successfully ran configuration file
/home/me/.config/borgmatic/config.yaml: Successfully ran configuration file

Expected behavior (if a bug)

Run only once.

Other notes / implementation ideas

Environment

borgmatic version: 1.5.1

Use sudo borgmatic --version or sudo pip show borgmatic | grep ^Version

borgmatic installation method: I think I used pip

Borg version: 1.1.15

Use sudo borg --version

Python version: Python 3.8.5

Use python3 --version

Database version (if applicable): [version here]

Use psql --version or mysql --version on client and server.

operating system and version: Ubuntu 20.04.1

#### What I'm trying to do and why When I run any borgmatic commands that calls borg, it runs them twice. #### Steps to reproduce (if a bug) ```yaml location: source_directories: - ~/somedit repositories: - host:repo one_file_system: true storage: encryption_passcommand: cat /passphrase retention: keep_daily: 7 keep_weekly: 4 keep_monthly: 6 keep_yearly: 1 consistency: checks: - repository - archives check_last: 3 ``` Run `borgmatic list` for example, and see that it runs the underlying borg command twice, showing the output twice. Same goes when making a backup: it makes the backup twice. But running `borgmatic --version` for instance only shows the output once. Same for `borg --version`: runs only once. #### Actual behavior (if a bug) ``` $ borgmatic list --verbosity 2 Ensuring legacy configuration is upgraded host:repo: Listing archives borg list --debug --show-rc host:repo using builtin fallback logging configuration 35 self tests completed in 0.11 seconds SSH command line: ['ssh', 'host', 'borg', 'serve', '--umask=077', '--debug'] Remote: using builtin fallback logging configuration Remote: using builtin fallback logging configuration Remote: Initialized logging system for JSON-based protocol Remote: Resolving repository path b'repo' Remote: Resolved repository path to '/data1/home/user/repo' Remote: Verified integrity of /data1/home/user/repo/index.1645 TAM-verified manifest security: read previous location 'ssh://host/./repo' security: read manifest timestamp '2021-01-26T08:14:38.103280' security: determined newest manifest timestamp as 2021-01-26T08:14:38.103280 security: repository checks ok, allowing access <backups list> RemoteRepository: 213 B bytes sent, 3.44 kB bytes received, 5 messages sent terminating with success status, rc 0 host:repo: Listing archives borg list --debug --show-rc host:repo using builtin fallback logging configuration 35 self tests completed in 0.10 seconds SSH command line: ['ssh', 'host', 'borg', 'serve', '--umask=077', '--debug'] Remote: using builtin fallback logging configuration Remote: using builtin fallback logging configuration Remote: Initialized logging system for JSON-based protocol Remote: Resolving repository path b'repo' Remote: Resolved repository path to '/data1/home/user/repo' Remote: Verified integrity of /data1/home/host/repo/index.1645 TAM-verified manifest security: read previous location 'ssh://host/./repo' security: read manifest timestamp '2021-01-26T08:14:38.103280' security: determined newest manifest timestamp as 2021-01-26T08:14:38.103280 security: repository checks ok, allowing access <same backups list> RemoteRepository: 213 B bytes sent, 3.45 kB bytes received, 5 messages sent terminating with success status, rc 0 summary: /etc/borgmatic.d/config.yaml: Successfully ran configuration file /home/me/.config/borgmatic/config.yaml: Successfully ran configuration file ``` #### Expected behavior (if a bug) Run only once. #### Other notes / implementation ideas #### Environment **borgmatic version:** 1.5.1 Use `sudo borgmatic --version` or `sudo pip show borgmatic | grep ^Version` **borgmatic installation method:** I think I used pip **Borg version:** 1.1.15 Use `sudo borg --version` **Python version:** Python 3.8.5 Use `python3 --version` **Database version (if applicable):** [version here] Use `psql --version` or `mysql --version` on client and server. **operating system and version:** Ubuntu 20.04.1
coaxial commented 2021-01-26 18:35:02 +00:00
Author
Copy Link

Oh nevermind, I'm an idiot. I had the same config file in my home and in /etc/borgmatic.d and that's why it was running it twice: once for each config file!

Oh nevermind, I'm an idiot. I had the same config file in my home and in `/etc/borgmatic.d` and that's why it was running it twice: once for each config file!
witten commented 2021-01-26 18:35:45 +00:00
Owner
Copy Link

Glad to hear you figured it out! Was just about to suggest something like that.

Glad to hear you figured it out! Was just about to suggest something like that.
witten added the
question / support
 label 2021-01-26 18:35:55 +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
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#386
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?