borgmatic-collective/borgmatic
borgmatic-collective/borgmatic
Watch
9
74
Fork
You've already forked borgmatic
 57
Code Issues 71 Pull requests 3 Releases 162 Packages 1 Activity Actions 1

trouble with new borgmatic version #878

New issue
Closed
opened 2024-06-06 13:43:21 +00:00 by barnybla · 4 comments
barnybla commented 2024-06-06 13:43:21 +00:00
Copy link

What I'm trying to do and why

I'm trying to makr backup and list backups with this error:

root@ax41:~# borgmatic list
ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41: Listing archives
passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect.
ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41: Error running actions for repository
Command '('borg', 'list', '--json', 'ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41')' returned non-zero exit status 2.
/etc/borgmatic/config.yaml: An error occurred

summary:
/etc/borgmatic/config.yaml: An error occurred
ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41: Error running actions for repository
Command '('borg', 'list', '--json', 'ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41')' returned non-zero exit status 2.``

Steps to reproduce

No response

Actual behavior

No response

Expected behavior

No response

Other notes / implementation ideas

No response

borgmatic version

1.8.11

borgmatic installation method

pipx install

Borg version

borg 1.2.4

Python version

Python 3.11.2

Database version (if applicable)

No response

Operating system and version

proxmox ve 8.2.2 / Debian 12

### What I'm trying to do and why I'm trying to makr backup and list backups with this error: root@ax41:~# borgmatic list ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41: Listing archives passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect. ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41: Error running actions for repository Command '('borg', 'list', '--json', 'ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41')' returned non-zero exit status 2. /etc/borgmatic/config.yaml: An error occurred summary: /etc/borgmatic/config.yaml: An error occurred ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41: Error running actions for repository Command '('borg', 'list', '--json', 'ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41')' returned non-zero exit status 2.`` ### Steps to reproduce _No response_ ### Actual behavior _No response_ ### Expected behavior _No response_ ### Other notes / implementation ideas _No response_ ### borgmatic version 1.8.11 ### borgmatic installation method pipx install ### Borg version borg 1.2.4 ### Python version Python 3.11.2 ### Database version (if applicable) _No response_ ### Operating system and version proxmox ve 8.2.2 / Debian 12
config.txt
33 KiB
witten commented 2024-06-06 16:46:59 +00:00
Owner
Copy link

The error message you're seeing from Borg means exactly what it says: The passphrase you're supplying is incorrect! Are you sure you're using the passphrase that you entered when creating your repository? If you want to eliminate borgmatic from the picture and just try this with plain Borg for debugging purposes, you can run Borg directly e.g.:

BORG_PASSPHRASE=... borg list --json ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41

Where ... is replaced with your actual passphrase. If that doesn't work with a similar error, then it'll tell you that the problem is probably the passphrase you're using.

Note: If that's your actual encryption passphrase in the configuration file, you're going to want to change it now that it's been posted publicly on the internet! This might be of help: https://borgbackup.readthedocs.io/en/stable/usage/key.html

The error message you're seeing from Borg means exactly what it says: The passphrase you're supplying is incorrect! Are you sure you're using the passphrase that you entered when creating your repository? If you want to eliminate borgmatic from the picture and just try this with plain Borg for debugging purposes, you can run Borg directly e.g.: ``` BORG_PASSPHRASE=... borg list --json ssh://xxxxxxxx@xxxxxxxx.your-storagebox.de:23/./backups/ax41 ``` Where `...` is replaced with your actual passphrase. If that doesn't work with a similar error, then it'll tell you that the problem is probably the passphrase you're using. Note: If that's your actual encryption passphrase in the configuration file, you're going to want to change it now that it's been posted publicly on the internet! This might be of help: https://borgbackup.readthedocs.io/en/stable/usage/key.html
barnybla commented 2024-06-07 08:22:32 +00:00
Author
Copy link

Thanks for reply,
No, the passphrase is not the aktual one.

I have running 4 backup jobs running on different servers, with different borgmatic versions. The Passphrase is the right on. Your command works perfect on another server (borg 1.2.6, borgmatic 1.8.2) Is there everyting changed in the Versions. Is there an howto for that error: passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect. What are the differences between BORG_PASSPHRASE, BORG_PASSCOMMAND and BORG_PASSPHRASE_FD

Bernd

Thanks for reply, No, the passphrase is not the aktual one. I have running 4 backup jobs running on different servers, with different borgmatic versions. The Passphrase is the right on. Your command works perfect on another server (borg 1.2.6, borgmatic 1.8.2) Is there everyting changed in the Versions. Is there an howto for that error: passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect. What are the differences between BORG_PASSPHRASE, BORG_PASSCOMMAND and BORG_PASSPHRASE_FD Bernd
witten commented 2024-06-09 00:41:26 +00:00
Owner
Copy link

Is there everyting changed in the Versions.

There are changes in every released version of borgmatic, but I can't immediately think of any particular changes between 1.8.2 and 1.8.11 that would cause the issue you're having here. But does your passphrase contain any special characters that might be getting interpreted differently between borgmatic versions? I'm thinking of characters like $ and/or { maybe interacting with #782 (which was introduced in borgmatic 1.8.5).

A related idea is to try changing your passphrase to something without special characters—both in the repository and borgmatic's configuration file—and see if that makes the problem go away. If it does, it may indicate the problem is the special characters.

Yet another idea is to try to set the (original) passphrase outside of borgmatic's configuration file to bypass any potential parsing problems. For instance, comment out the encryption_passphrase option in your configuration file and then set the environment variable manually when calling borgmatic. Example:

BORG_PASSPHRASE='mypassphrase' borgmatic -v 1 create

That passphrase value should make its way to Borg without any borgmatic interference.

Is there an howto for that error: passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect.

Not that know of. But it's just a fancy way of Borg saying: "I received a passphrase that's incorrect for this repository."

What are the differences between BORG_PASSPHRASE, BORG_PASSCOMMAND and BORG_PASSPHRASE_FD

The documentation on that is here: https://borgbackup.readthedocs.io/en/stable/usage/general.html#environment-variables

> Is there everyting changed in the Versions. There are changes in every released version of borgmatic, but I can't immediately think of any *particular* changes between 1.8.2 and 1.8.11 that would cause the issue you're having here. But does your passphrase contain any special characters that might be getting interpreted differently between borgmatic versions? I'm thinking of characters like `$` and/or `{` maybe interacting with #782 (which was introduced in borgmatic 1.8.5). A related idea is to try changing your passphrase to something without special characters—both in the repository and borgmatic's configuration file—and see if that makes the problem go away. If it does, it may indicate the problem is the special characters. Yet another idea is to try to set the (original) passphrase outside of borgmatic's configuration file to bypass any potential parsing problems. For instance, comment out the `encryption_passphrase` option in your configuration file and then set the environment variable manually when calling borgmatic. Example: ``` BORG_PASSPHRASE='mypassphrase' borgmatic -v 1 create ``` That passphrase value should make its way to Borg without any borgmatic interference. > Is there an howto for that error: passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect. Not that know of. But it's just a fancy way of Borg saying: "I received a passphrase that's incorrect for this repository." > What are the differences between BORG_PASSPHRASE, BORG_PASSCOMMAND and BORG_PASSPHRASE_FD The documentation on that is here: https://borgbackup.readthedocs.io/en/stable/usage/general.html#environment-variables
witten commented 2024-08-11 17:53:38 +00:00
Owner
Copy link

I'm closing this due to inactivity, but I'd be happy to revisit if there's anything else to discuss.

Also, I should mention the related ticket https://github.com/borgmatic-collective/docker-borgmatic/issues/346 here. I don't think it's the same issue you're having since you're not using a container install of borgmatic, but it might help somebody else with a similar issue who is actually using a container.

I'm closing this due to inactivity, but I'd be happy to revisit if there's anything else to discuss. Also, I should mention the related ticket https://github.com/borgmatic-collective/docker-borgmatic/issues/346 here. I don't think it's the same issue you're having since you're not using a container install of borgmatic, but it might help somebody else with a similar issue who is actually using a container.
witten 2024-08-11 17:53:40 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
parallel-borgmatic
command-hook-steps
2.1.7
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
2.1.1
2.1.0
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
1.9.14
1.9.13
1.9.12
1.9.11
1.9.10
1.9.9
1.9.8
1.9.7
1.9.6
1.9.5
1.9.4
1.9.3
1.9.2
1.9.1
1.9.0
1.8.14
1.8.13
1.8.12
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   
blocked

   
breaking

   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No labels
blocked
breaking
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#878
No description provided.