On 21 Apr 2020, at 12:09, Pim Rupert <p...@lemonbit.com> 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 process manually from the shell. # su - backuppc -s /bin/bash -bash-4.2$ /usr/bin/perl /usr/share/BackupPC/bin/BackupPC_dump -i mysqlimport.paragin.nl __bpc_progress_state__ pre-cmd __bpc_progress_state__ backup share "/" started incr dump, share=/ xferPids 19255 xferPids 19255,19259 __bpc_progress_fileCnt__ 1 __bpc_progress_fileCnt__ 21 __bpc_progress_fileCnt__ 41 (...) __bpc_progress_state__ rename total xferPids xferPids incr backup complete -bash-4.2$ echo $? 0 I saw backup traffic via tcpdump and successful authentication on jump host and client host. This succeeds just fine! However, when started from the BackupPC web interface, the backup fails when a jump host is configured. So, again, just speculating, but could it be that I am hitting a bug in the web interface? Is anyone else seeing the same behaviour in their setups when using the BackupPC web interface? Unfortunately my Perl is too rusty for proper debugging. Best regards, Pim Rupert _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
