Hi Falko,
>> Apparently a shell is required to use a jump host from the ssh command in
>> this situation?
>
> There's an analysis about apparently same problem:
>
> https://unix.stackexchange.com/questions/457692/does-ssh-proxyjump-require-local-shell-access
>
> They mention, that setting the
Hi Pim,
The reason for this had nothing to do with any "remote host", it was that the
"backuppc" user had no shell configured!
# grep backuppc /etc/passwd
backuppc:x:994:990::/var/lib/BackupPC:/sbin/nologin
After changing the shell to /bin/bash for backuppc, all errors disappe
Hello,
Some good news for anyone following this issue. ;-)
> On 22 Apr 2020, at 13:38, Pim Rupert wrote:
>
> When it fails, it fails on the rsync_bpc command. With the following error
> (example):
>
>Xfer PIDs are now 31322
>This is the rsync child about to exec /usr/bin/rsync_bpc
>
Hello Falko,
> On 22 Apr 2020, at 09:59, Falko Trojahn via BackupPC-users
> wrote:
>
> Usually, there are some more informations in the Xferlog. What shows the
> Xferlog of a failed attempt?
The XferLog and verbose output for three attempts are attached below.
The same user is used for all
Hi Pim,
Without DumpPreUserCmd I get the following error when initiating an incremental
backup through the web interface:
Got fatal error during xfer (rsync error: unexplained error (code 255)
at io.c(226) [Receiver=3.1.2.0])
that reminds me, that I'm using rsync-bpc version 3.0.9.14
Hi Greg and Falko
> On 21 Apr 2020, at 20:09, Greg Harris wrote:
>
> You seem to have a pretty good handle on stuff, but you aren’t suffering from
> CentOS’ silent killer are you? SELinux?
Thank for the suggestion. Unfortunately it's not SELinux, I have it fully
disabled to be certain.
> On
You seem to have a pretty good handle on stuff, but you aren’t suffering from
CentOS’ silent killer are you? SELinux?
Thanks,
Greg Harris
On Apr 21, 2020, at 8:10 AM, Falko Trojahn via BackupPC-users
mailto:backuppc-users@lists.sourceforge.net>>
wrote:
Hi Pim,
using jumphost here for backi
Hello Pim,
using jumphost here for backing up a remote host and it's VMs without
any problems. What BackupPC version do you use?
I am using BackupPC 4.3.1-3 from the yum repository for CentOS 7. Very
good to hear that you got it working on your installation.
ok, so I'll try it on an 4.3.2 ins
Hi Pim,
using jumphost here for backing up a remote host and it's VMs without any
problems. What BackupPC version do you use?
I am using BackupPC 4.3.1-3 from the yum repository for CentOS 7. Very good to
hear that you got it working on your installation.
ok, so I'll try it on an 4.3.2 inst
On 21 Apr 2020, at 12:09, Pim Rupert wrote:
>
> I am just speculating here, but could it be that when the BackupPC software
> is handling the SSH process, it is somehow unable to deal with the implictly
> added ProxyCommand arguments?
Following this hunch I tried starting the BackupPC_dump pro
Hi Falko,
> On 21 Apr 2020, at 00:03, Falko Trojahn via BackupPC-users
> wrote:
>
> using jumphost here for backing up a remote host and it's VMs without any
> problems. What BackupPC version do you use?
I am using BackupPC 4.3.1-3 from the yum repository for CentOS 7. Very good to
hear that
Hi,
Option B: using an SSH client config file
Alternatively I have tried using an implicit jump host through SSH client
config with a slightly different way of setting up the jump host (through
netcat). This results in exactly the same errors.
Host client-machine
ProxyCommand ssh jumphost
12 matches
Mail list logo
