Per-host config files are working fine for me. Maybe your
RsyncClientCmd has the rsync path hardcoded in it instead of referencing
$rsyncPath?
My environment is mostly-linux with a few BSD-based hosts and, to just
pick a <client>.pl that contains "local" at random-ish, I have:
$Conf{RsyncClientPath} = 'sudo /usr/local/bin/rsync';
# $Conf{RsyncClientPath} = 'sudo /tmp/rsync';
$Conf{RsyncClientCmd} = '$sshPath $host nice $rsyncPath $argList+';
$Conf{RsyncClientRestoreCmd} = '$sshPath $host nice $rsyncPath $argList+';
On 7/24/21 6:27 AM, Brad Alexander wrote:
I ran across what appears to be the reason for the issue that I am
having. I found the following issue in my console:
/var/log/console.log:Jul 23 23:52:11 danube kernel: Jul 23 23:52:11
danube sudo[2
866]: backuppc : command not allowed ; PWD=/usr/home/backuppc ;
USER=root ; COMMA
ND=/usr/bin/rsync --server --sender -slHogDtprcxe.iLsfxC
I don't quite understand it. It appears that
$Conf{RsyncClientPath} = 'sudo /usr/bin/rsync';
in my config.pl <http://config.pl> is overriding
$Conf{RsyncClientPath} = 'sudo /usr/local/bin/rsync';
in my freebsd hosts .pl files. Are per-host config files no longer
supported? Is there another way to specify the path for the rsync
command on a per-host or per-OS basis?
Thanks,
--b
On Fri, Jul 23, 2021 at 4:28 PM Brad Alexander <stor...@gmail.com
<mailto:stor...@gmail.com>> wrote:
I have been running BackupPC 3.x for many years on a Debian Linux
box. I just expanded my TrueNAS box with larger drives, grew my
pool, and am in the process of converting from BackupPC 3.3.1 on
the dedicated server (that has gotten a bit snug on the drive
space) to a 4.4.0 install in a FreeBSD jail on my TrueNAS box,
using the guide at
https://www.truenas.com/community/threads/quickstart-guide-for-backuppc-4-in-a-jail-on-freenas.74080/
<https://www.truenas.com/community/threads/quickstart-guide-for-backuppc-4-in-a-jail-on-freenas.74080/>,
and another page for the changes needed for rsync. I am backing up
both FreeBSD and Linux boxes.
So at this point, the linux boxes are backing up on the 4.4
installation, but the FreeBSD boxes are not. Both are working on
the 3.3.1 machine. I transferred all of my <hostname>.pl files
from the old backup box to the 4.4.0 jail, and they are identical
to the old configs. So does anyone have any ideas about what could
be happening? I have a log of an iteration of the backup test at
https://pastebin.com/KLKxGYT1 <https://pastebin.com/KLKxGYT1>
It is stopping to ask for a password, which it shouldn't be doing,
unless it is looking for rsync_bpc on the client machines.
Thoughts?
Thanks,
--b
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
