On 1/29/2018 2:53 PM, RAKOTONDRAINIBE Harimino Lalatiana wrote:
The backuppc is installed in freebsd 11.1
All hosts seems to be backuppc well except the localhost.
I did like it was said in the forum so I build rsync-bpc 3.0.9 from current
git .
BTW, You could use ports:
net/rsync-bpc
What happens when you run this command as the backuppc user?
su backuppc
/usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync --server
--sender -svvlHogDtpre.iLsf
Is there any output? Does it exit immediately?
Craig
On Mon, Jan 29, 2018 at 3:53 AM, RAKOTONDRAINIBE Harimino Lalatiana
Alex,
yes I understand your points and they may apply in most backup scenarios.
However, in my case it's a little bit different:
I'm saving lucene indices, which currently rely on results of a postgres
database process. The problem with lucene is that a partitial backup of an
index will
make
Hi everyone,
After an issues with backuppc v3 , I upgraded to v4.1.4.
The backuppc is installed in freebsd 11.1
All hosts seems to be backuppc well except the localhost.
I did like it was said in the forum so I build rsync-bpc 3.0.9 from
current git .
In addition to that I run :
Hi Graig,
Nothing happen after I run the command, I will open a new thread then to
avoid confusion.
Thank you
Regards,
Hari
2018-01-27 20:27 GMT+03:00 Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net>:
> Hari,
>
> This doesn't look related to the original thread. For
Hi Alexander, Graig
I installed the backuppc4 and p5-BackupPC-XS via ports. And I reinstalled
the rsync-bpc via ports.
Anyway their still no output for the command below and yes it exit
immediately:
backuppc@backup:/ % /usr/bin/ssh -q -x -l backuppc localhost
/usr/local/bin/rsync --server
So I it seems hat the issue is about DNS lookup error: general failure when
I run ssh .
backuppc@backup:/ % /usr/bin/ssh -v -x -l backuppc localhost /bin/foobar
OpenSSH_7.2p2, OpenSSL 1.0.2k-freebsd 26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to
Please remove the -q option. Try adding -v (or even -vv) to the ssh args.
What happens if you run some other command, eg, /bin/date? What happens if
you run some path that doesn't exist, eg, /bin/foobar.
Examples:
/usr/bin/ssh -v -x -l backuppc localhost /bin/date
/usr/bin/ssh -v -x -l
