Re: [BackupPC-users] backup failed (received signal=ALRM)

Ok, that confirms this is the same issue. Rsync 3.2.3 made a change that unfortunately exposed a long-standing bug in File::RsyncP. The new version of File::RsyncP fixes that issue. Craig On Tue, Nov 17, 2020 at 10:41 AM Marcus Hardt wrote: > To add the rsync versions: > > backkupc side:

Re: [BackupPC-users] backup failed (received signal=ALRM)

To add the rsync versions: backkupc side: 3.1.3-6 remote side: 3.2.3-2 M. On 11/17/20 10:01, Marcus Hardt wrote: > Hi There, > > I've seen this error on some hosts for quite a while now, and ignored it. > > Recently I took the time to look a bit deeper. > > Started the backup from the

Re: [BackupPC-users] backup failed (received signal=ALRM)

Are you using BackupPC 3.x with rsync? Was your client rsync version recently upgraded to 3.2.3? If so, see this issue . The solution is to upgrade File::RsyncP to version 0.76. Craig On Tue, Nov 17, 2020

[BackupPC-users] backup failed (received signal=ALRM)

Hi There, I've seen this error on some hosts for quite a while now, and ignored it. Recently I took the time to look a bit deeper. Started the backup from the commandline like: /usr/share/backuppc/bin/BackupPC_dump -v -i nemo > logfile 2>&1 I was rather surprised seeing a 4.8GB logfile