Unable to borgmatic create (borgbase) #481

Closed
opened 2021-12-16 11:17:39 +00:00 by borgwarrior · 3 comments

What I'm trying to do and why

Unable to start a remote borgbase backup with borgmatic create

Steps to reproduce (if a bug)

Created and initialized a repo on borgbase, added a public key through the web interface. Installed and edited a borgmatic config file according to my own configuration. I proceeded to try creating a backup through the borgmatic create command. This results in a repeated prompt for my repo password. I enter what I am certain is my repo password but receive another identical prompt for my password. No success despite repeated attempts so I exit the prompt with the ctrl + c command. I do not have my ssh key pair locally encrypted so I dont think it is requesting the password for that but rather the password for my repo. Results of sudo borgmatic create pasted below. I've tried deleting and creating new repos through the borgbase web interface and then initializing through the shell and noticed that I am not always prompted to choose a password to encrypt my backup with (not sure if that helps). Much appreciated.

Thu Dec 16 06:12:27 AM EST 2021 - Starting backup
@.repo.borgbase.com's password:
@.repo.borgbase.com's password:
Traceback (most recent call last):
File "/usr/bin/borgmatic", line 33, in
sys.exit(load_entry_point('borgmatic==1.5.21', 'console_scripts', 'borgmatic')())
File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 823, in main
summary_logs = parse_logs + list(collect_configuration_run_summary_logs(configs, arguments))
File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 721, in collect_configuration_run_summary_logs
results = list(run_configuration(config_filename, config, arguments))
File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 138, in run_configuration
yield from run_actions(
File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 337, in run_actions
json_output = borg_create.create_archive(
File "/usr/lib/python3.10/site-packages/borgmatic/borg/create.py", line 288, in create_archive
return execute_command(full_command, output_log_level, output_file, borg_local_path=local_path)
File "/usr/lib/python3.10/site-packages/borgmatic/execute.py", line 217, in execute_command
log_outputs(
File "/usr/lib/python3.10/site-packages/borgmatic/execute.py", line 72, in log_outputs
(ready_buffers, _, _) = select.select(output_buffers, [], [])
KeyboardInterrupt

borgmatic version: 1.5.21

borgmatic installation method:

Installed Borgmatic through Fedora's package manager. sudo dnf install borgmatic.

Borg version: borg 1.1.17 .

Installed through Fedora's package manager sudo dnf install borgbackup

Python version: Python 3.10.0

Use python3 --version

Database version (if applicable): [version here]

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

operating system and version:

Fedora 35

#### What I'm trying to do and why Unable to start a remote borgbase backup with borgmatic create #### Steps to reproduce (if a bug) Created and initialized a repo on borgbase, added a public key through the web interface. Installed and edited a borgmatic config file according to my own configuration. I proceeded to try creating a backup through the borgmatic create command. This results in a repeated prompt for my repo password. I enter what I am certain is my repo password but receive another identical prompt for my password. No success despite repeated attempts so I exit the prompt with the ctrl + c command. I do not have my ssh key pair locally encrypted so I dont think it is requesting the password for that but rather the password for my repo. Results of sudo borgmatic create pasted below. I've tried deleting and creating new repos through the borgbase web interface and then initializing through the shell and noticed that I am not always prompted to choose a password to encrypt my backup with (not sure if that helps). Much appreciated. Thu Dec 16 06:12:27 AM EST 2021 - Starting backup *******@*******.repo.borgbase.com's password: *******@*******.repo.borgbase.com's password: Traceback (most recent call last): File "/usr/bin/borgmatic", line 33, in <module> sys.exit(load_entry_point('borgmatic==1.5.21', 'console_scripts', 'borgmatic')()) File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 823, in main summary_logs = parse_logs + list(collect_configuration_run_summary_logs(configs, arguments)) File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 721, in collect_configuration_run_summary_logs results = list(run_configuration(config_filename, config, arguments)) File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 138, in run_configuration yield from run_actions( File "/usr/lib/python3.10/site-packages/borgmatic/commands/borgmatic.py", line 337, in run_actions json_output = borg_create.create_archive( File "/usr/lib/python3.10/site-packages/borgmatic/borg/create.py", line 288, in create_archive return execute_command(full_command, output_log_level, output_file, borg_local_path=local_path) File "/usr/lib/python3.10/site-packages/borgmatic/execute.py", line 217, in execute_command log_outputs( File "/usr/lib/python3.10/site-packages/borgmatic/execute.py", line 72, in log_outputs (ready_buffers, _, _) = select.select(output_buffers, [], []) KeyboardInterrupt **borgmatic version:** 1.5.21 **borgmatic installation method:** Installed Borgmatic through Fedora's package manager. sudo dnf install borgmatic. **Borg version:** borg 1.1.17 . Installed through Fedora's package manager sudo dnf install borgbackup **Python version:** Python 3.10.0 Use `python3 --version` **Database version (if applicable):** [version here] Use `psql --version` or `mysql --version` on client and server. **operating system and version:** Fedora 35
witten added the
question / support
label 2021-12-16 17:20:31 +00:00
Owner

Thank you for filing this! The password prompt you're seeing is actually coming directly from ssh for connecting to the remote host. Borg's repository passphrase prompt instead looks like: Enter passphrase for key test.borg:

So what I would suggest is to double check that you're configured Borgbase with your ssh public keys. Once that's set up properly, I believe that you would no longer be prompted for a password to connect to Borgbase. Here are the Borgbase docs on that: https://docs.borgbase.com/faq/ssh/ ... Although given that you already presumably have local SSH keys generated, the one step that remains is to confirm that they're set up in Borgbase's Account > SSH Keys UI.

Please let me know if that helps!

Thank you for filing this! The password prompt you're seeing is actually coming directly from ssh for connecting to the remote host. Borg's repository passphrase prompt instead looks like: `Enter passphrase for key test.borg:` So what I would suggest is to double check that you're configured Borgbase with your ssh public keys. Once that's set up properly, I believe that you would no longer be prompted for a password to connect to Borgbase. Here are the Borgbase docs on that: https://docs.borgbase.com/faq/ssh/ ... Although given that you already presumably have local SSH keys generated, the one step that remains is to confirm that they're set up in Borgbase's **Account > SSH Keys** UI. Please let me know if that helps!
Author

Thank you so much. deleted the key pairs,the repository and started all over, borgmatic works flawlessly now. However I'm having problems automating with both crontabs and systemd timers. Judging from the preexisting/solved issues its either a problem with my $PATH or flawed permissions somewhere. Guess I'll start a new issue solely for that. Thanks again. Really appreciate the work that you do.

Thank you so much. deleted the key pairs,the repository and started all over, borgmatic works flawlessly now. However I'm having problems automating with both crontabs and systemd timers. Judging from the preexisting/solved issues its either a problem with my $PATH or flawed permissions somewhere. Guess I'll start a new issue solely for that. Thanks again. Really appreciate the work that you do.
Owner

Glad to hear that did it, at least for this particular issue!

Glad to hear that did it, at least for this particular issue!
Sign in to join this conversation.
No Milestone
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#481
No description provided.