Hi there,

On Wed, 3 Jun 2026, Matthias@... wrote:

It looks like I have an issue with my config files in /etc/backuppc.
For two hosts I get an error (xfer start failed:
$Conf{RsyncBackupPCPath} is set to , which isn't a valid executable)

But it is only configured in /etc/backuppc/config.pl. Not in any other of my 30 
host:
  grep -i RsyncBackupPCPath /etc/backuppc/*.pl
  /etc/backuppc/config.pl:$Conf{RsyncBackupPCPath} = 
'/usr/libexec/backuppc-rsync/rsync_bpc';
  /etc/backuppc/config.pl:  'RsyncBackupPCPath' => '0',

I'd be happy for any hint :)

Have you used the Web interface to edit the configuration?  Using the
Web GUI, more than once by accident I have managed to create an array
with an empty element.  Occasionally that would break things.  I have
considered adding a check for empty array elements in the GUI code but
it isn't a high priority.  I recommend you look at the configuration
very carefully using a text editor or a pager.

Where are all your per-PC configurations stored?  Are they all in the
/etc/backuppc/ directory?  We may need to see the full configuration,
at least config.pl plus the two failing hosts and maybe one that's OK.
Most systems have a separate directory for the per-PC configuration
files, it seems a lot tidier to me, that's how BackupPC sets it up if
you install from upstream and that's how I do it.  I guess Debian has
its own ideas.  I don't understand the logic of deliberately changing
what seems to me a perfectly serviceable arrangement for everyone, but
if there's a rational explanation I'm willing to listen.  Anyway if a
per-PC configuration isn't in the BackupPC configuration directory you
obviously won't find it with the grep command that you gave.

Have you edited any of the BackupPC Perl scripts?

--

73,
Ged.


_______________________________________________
BackupPC-users mailing list
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Reply via email to