Got unexpected RPC data format from server #424
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#424
Loading…
Reference in New Issue
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?
What I'm trying to do and why
I'm trying to initialize a repo with
sudo borgmatic init --encryption repokey
on a Hentzer Storage Box. I'm following the steps on https://torsion.org/borgmatic/docs/how-to/set-up-backups/#initializationSteps to reproduce (if a bug)
Config:
Actual behavior (if a bug)
Expected behavior (if a bug)
However, when I run
borg init --encryption repokey --debug ssh://u11111@u11111.your-storagebox.de:23/./backups/pc
manually it works correctly.Other notes / implementation ideas
Environment
borgmatic version: 1.5.14
borgmatic installation method: pip (global)
Borg version: borg 1.1.15
Python version: Python 3.6.9
operating system and version: Ubuntu 18.04.5 LTS
I'm not entirely sure what's going on here, but have you tried directly running the Borg command that borgmatic is initially tripping up on? Example:
Standalone
borg
commands were working fine.Anyway, I upgraded my Ubuntu to 20.04 and installed borgmatic through
apt
(although at version 1.5.1). Everything seems to work now.The only other thing I changed was
ssh_command
option in preferences. Previously I had it set tossh u11111@u11111.your-storagebox.de -F /home/user/.ssh/config -p 23
and it's possible the duplicated user@hostname part caused problems. You can see it in theSSH command line:
section of my debug log above.Glad to hear it's working now!