Hi,
jerome winmedia wrote on 2018-08-06 15:29:45 +0200 [[BackupPC-users] Backuppc |
Got fatal error during xfer (aborted by signal=PIPE)]:
> I am running backuppc version 3.3.1 on an Ubuntu 16.04.5 LTS, I try to
> backup several Linux servers, almost Debian, ubuntu or proxmox hosts.
>
> My issue is that when I run the Full/Incermental backup from webUI I got
> the message:
>
> 2018-08-06 14:22:32 full backup started for directory /var/lib/vz/dump/dump
> (baseline backup #1) 2018-08-06 14:22:33 Aborting backup up after signal
> PIPE 2018-08-06 14:22:34 Got fatal error during xfer (aborted by
> signal=PIPE) <
this is a very generic error message, about as specific as "something went
wrong", but it turns out to be quite obvious, if you look close enough (and
thank you for providing all the necessary information for making that
possible!):
> [...]
> Running: /usr/bin/ssh -o ServerAliveInterval=300 -q -x -l root HOST
> /usr/bin/rsync --server --sender --protocol=29 --numeric-ids --perms --owner
> --group -D --links --hard-links --times --block-size=2048 --ignore-times .
> /var/lib/vz/dump/dump/
You ignored the comment about $Conf{RsyncArgs} - "Do not edit the first set
unless you have a thorough understanding of how File::RsyncP works". I
strongly doubt you should be setting "--protocol=29", but thank you for
doing so and thereby making me have a closer look at the rsync arguments.
"--protocol=29" is probably not the problem *here* (it may well be if that
is not what would be automatically selected anyway), but rather what is
*missing*: "--recursive". If you continue looking, you'll notice:
> Remote[2]: skipping directory .
... and with that the backup was finished, as far as the remote rsync was
concerned. It was supposed to non-recursively backup a directory, which
means "do nothing". It did exactly that. BackupPC, on the other hand, was
expecting more than this.
Re-add "--recursive" to $Conf {RsyncArgs}. I doubt you meant to remove it
in the first place. Better yet, don't set $Conf {RsyncArgs} in your HOST.pl
and don't change the default in config.pl. There should very rarely be any
reason to do so (except for adding "--checksum-seed=32761", and even that
might be better placed in $Conf {RsyncArgsExtra}).
> [...]
> When I run the rsync command manually, the backup is started correctly:
>
> rsync -av -e ssh root@HOST:/var/lib/vz/dump/dump
> /mnt/backuppc/backuppc/pc/pHOST/2<
Well, yes, it's a different command, isn't it? Note that you should *not*
really be using a BackupPC host directory as target for a plain rsync command.
That is *not* the same as what BackupPC does! Be sure to remove that directory
after testing.
Hope that helps.
Regards,
Holger
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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/
