On 02/10/2017 06:08 AM, heiko.helmle at horiba.com wrote:
> "Borgbackup" <borgbackup-bounces+heiko.helmle=horiba.com at python.org>
> wrote on 10.02.2017 14:49:59:
>
>> > this is a strange issue - i get this only on one system (yet). (SLES 12
>> > SP2)
>> How is that system different from your other systems (on which you use
>> the same binary)?
>
> this is the first SLES12SP2 System I tried. The others were CentOS,
> Ubuntu and Debian.
Hmm, might be a SUSE thing. I just tried on my openSUSE Leap 42.2:
aklaver at tito:~> borg init ssh://arkansas
Remote: ssh: Could not resolve hostname arkansa: Name or service not known
Cheating works:
aklaver at tito:~> borg init --remote-path /home/aklaver/bin/borg
ssh://arkansass
Enter new passphrase:
Or specifying IP:
aklaver at tito:~> borg_new init ssh://aklaver@xxx.xxx.xxx.xx
The authenticity of host 'xxx.xxx.xxx.x (xxx.xxx.xxx.x)' can't be
established.
>
>> > I'm using borg 1.0.9, the "all in one" binary from the github page and
>> > it seems to cut off the last letter from the hostname...
>> Give the sha256sum of the binary you use, please.
>
> # sha256sum /usr/local/bin/borg-linux64-1.0.9
> 9fa23310aa8b08a5d7427970250d9ec0f9512b03bbac32659079df8ae1031764
> /usr/local/bin/borg-linux64-1.0.9
>
> there's a symlink to this binary in /usr/local/bin/borg
>
>> That might be a pyinstaller bootloader issue.
>> Can you try 1.0.10rc1 ?
>
> tried and that one's better:
> # borg-linux64-1.0.10rc1 init ssh://testmachine
> usage: borg-linux64-1.0.10rc1 init [-h] [--critical] [--error] [--warning]
> [--info] [--debug] [--lock-wait N]
> [--show-rc] [--no-files-cache]
> [--umask M]
> [--remote-path PATH]
> [-e {none,keyfile,repokey}] [-a]
> [REPOSITORY]
> borg-linux64-1.0.10rc1 init: error: argument REPOSITORY: Invalid
> location format: "ssh://testmachine"
>
>> Try the normal linux64 binary as well as the pyi321-debug one.
>
> The py321-debug one does it right too.
>
>> > adding a space to the end fixes the name: (well obviously testname
>> > doesn't exist, but it's looking up the right name now)
>>
>> Sounds like an off-by-one error. Just strange this did not surface
> before.
>
> Yes - I'm also confused - I used borg on quite a lot of systems and this
> is the first that's having this problem. Maybe some environment variable
> influencing this that's only set on this system? I didn't find a clue
> yet...
>
> Best Regards
> Heiko Helmle
>
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>
--
Adrian Klaver
adrian.klaver at aklaver.com