[BackupPC-users] Fwd: After migration to V4, rsync backups not working

2017-03-16 Thread ads
Thank you Holger and Craig, that is most useful.

I use Arch Linux, and installed (upgraded) backuppc using the provided
package in pacman format. I already suspected configure.pl hadn't been run,
because I had to manually adjust RsyncBackupPCPath (it was empty)
and PoolV3Enabled (it was off).

I couldn't find a copy of configure.pl on my system. I guess the package
gets expanded in some temporary location which is cleaned after install. I
will have a more thorough search.

I think my choices now are:

1) Get a copy of configure.pl and run it. I haven't looked at it, and I
don't know perl. Is it something that needs to be run from a particular
location? I would also report the issue to the package maintainer.

2) Uninstall the packaged version and get the tar.gz file and install
myself manually.

I think I'd like to try 1 first.

Once again, thanks for your help.

On 15 March 2017 at 21:16, Craig Barratt 
wrote:

> Holger asked the right questions.  Yes, it's an ssh problem, as you note.
> You've come across what is one of the more likely upgrade issues.
>
> In looking at your rsync_bpc command, it doesn't look like
> $Conf{RsyncArgs} was updated when you installed 4.0, or you have a per-host
> override.
>
> Here's what a typical rsync_bpc command should look like:
>
> /usr/local/bin/rsync_bpc --bpc-top-dir /data/BackupPC4 --bpc-host-name
> HOSTNAME --bpc-share-name /LOCALPATH --bpc-bkup-num 0 --bpc-bkup-comp 3
> --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 1
> --bpc-attrib-new --bpc-log-level 1 -e /usr/bin/ssh -l root
> --rsync-path=/usr/local/bin/rsync --super --recursive --numeric-ids
> --perms --owner --group -D --times --links --hard-links --delete --partial
> --log-format=log: %o %i %B %8U,%8G %9l %f%L --stats --checksum
> HOSTNAME:/LOCALPATH/ /
>
> The "-e" option is built from $Conf{SshPath} and $Conf{RsyncSshArgs}.  The
> rest of the configurable arguments (after -e) come from $Conf{RsyncArgs}.
> As Holger mentions, either the main config.pl didn't get updated for some
> reason (did you install by running configure.pl?) or you have per-client
> overrides that the upgrade doesn't automatically update for you.
>
> The default settings in 4.0 for these config variables are:
>
> $Conf{RsyncArgs} = [
> '--super',
> '--recursive',
> '--protect-args',
> '--numeric-ids',
> '--perms',
> '--owner',
> '--group',
> '-D',
> '--times',
> '--links',
> '--hard-links',
>     '--delete',
> '--partial',
> '--log-format=log: %o %i %B %8U,%8G %9l %f%L',
> '--stats',
>
> $Conf{RsyncSshArgs} = [
> '-e', '$sshPath -l root',
> ];
>
>
> Craig
>
> On Wed, Mar 15, 2017 at 8:46 AM, Holger Parplies 
> wrote:
>
>> Hi,
>>
>> ads wrote on 2017-03-15 11:46:39 + [[BackupPC-users] After migration
>> to V4, rsync backups not working]:
>> > I have migrated from V3 to V4,
>>
>> how did you do that? By running configure.pl?
>>
>> > and now my rsync backups are not working. [...] The 3 'Permission
>> denied'
>> > lines look as if they might be ssh permission problems.
>>
>> I agree with that conclusion.
>>
>> Craig recently wrote on [backuppc-devel]:
>> > The configure.pl script updates the relevant rsync settings in the main
>> > config.pl file.  In particular, it updates $Conf{RsyncArgs}
>> > and $Conf{RsyncRestoreArgs} with the 4.0 settings.
>> >
>> > $Conf{RsyncSshArgs} is a new 4.0 setting, and $Conf{RsyncClientCmd}
>> > and $Conf{RsyncClientRestoreCmd} are no longer used.  configure.pl
>> tries to
>> > extract a sensible default setting for $Conf{RsyncSshArgs} from
>> > $Conf{RsyncClientCmd}.
>> >
>> > The potential problems are that there are per-client overrides for these
>> > settings (which is not checked by configure.pl), and the computed
>> value for
>> > $Conf{RsyncSshArgs} isn't correct.
>>
>> I'm guessing something went wrong. Either you have per-client overrides or
>> the value of RsyncSshArgs is computed incorrectly. What was your (V3)
>> RsyncClientCmd, what is your (V4) RsyncSshArgs?
>>
>> Regards,
>> Holger
>>
>> 
>> --
>> Check out the v

[BackupPC-users] After migration to V4, rsync backups not working

2017-03-15 Thread ads
Hello,

I have migrated from V3 to V4, and now my rsync backups are not working. I
have copied the latest log info below.

As you can see, I am trying to use rsync_bpc, but there is some kind of
permission problem. The permissions on the server look ok to me. The 3
'Permission denied' lines look as if they might be ssh permission problems.
The hostname (as far as backuppc is concerned) is jc, the host name (which
I can ping and ssh into) is jc-arch. The ClientNameAlias is set to jc-arch,
and in V3 backups have worked fine for a long while - a couple of years at
least. How can I find out the command that is causing the Permission denied
errors? I have tried copying the jc config to one called jc-arch, in case
the ClientNameAlias is not working, but I get exactly the same result.

Thank you for any assistance

XferLOG file /var/lib/backuppc/pc/jc/XferLOG.661.z created 2017-03-15
11:07:10
Backup prep: type = incr, case = 6, inPlace = 1, doDuplicate = 0,
newBkupNum = 661, newBkupIdx = 13, lastBkupNum = , lastBkupIdx =
 (FillCycle = 0, noFillCnt = 6)
Running: /usr/share/backuppc/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc
--bpc-host-name jc --bpc-share-name /home/jon --bpc-bkup-num 661
--bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1
--bpc-bkup-inode0 124144 --bpc-attrib-new --bpc-log-level 8
--rsync-path=/usr/bin/rsync --numeric-ids --perms --owner --group -D
--links --hard-links --times --block-size=2048 --recursive
--checksum-seed=32761 --one-file-system --exclude=.cache
--exclude=Downloads --exclude=tmp
--exclude=projects/oxpat/websites/ocs_backups/public_html
jc-arch:/home/jon/ /
incr backup started for directory /home/jon
Xfer PIDs are now 3994
This is the rsync child about to exec /usr/share/backuppc/bin/rsync_bpc
bpc_lib_conf_init: topDir = /var/lib/backuppc, logLevel = 8
bpc_path_create(/var/lib/backuppc/pc/jc/661)
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
= 0
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
rsync_bpc: connection unexpectedly closed (0 bytes received so far)
[Receiver]
bpc_sysCall_cleanup: doneInit = 1
RefCnt Deltas for new backup
Uncompressed HT:
Compressed HT:
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 124144 inode
Parsing done: nFilesTotal = 0
rsync error: error in rsync protocol data stream (code 12) at io.c(629)
[Receiver=3.0.9.5]
rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync
protocol data stream (code 12) at io.c(629) [Receiver=3.0.9.5])
Xfer PIDs are now
Got fatal error during xfer (rsync error: error in rsync protocol data
stream (code 12) at io.c(629) [Receiver=3.0.9.5])
Backup aborted (rsync error: error in rsync protocol data stream (code 12)
at io.c(629) [Receiver=3.0.9.5])
BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace =
1, lastBkupNum =
BackupFailCleanup: inPlace with no new files... no cleanup
Running BackupPC_refCountUpdate -h jc -f on jc
Xfer PIDs are now 4002
BackupPC_refCountUpdate: host jc #661: gotFsck = 1, gotDelta = , gotPoolCnt
= 1, gotNoPoolCntOk =
BackupPC_refCountUpdate: processing host jc #661 (fsck = 1)
BackupPC_refCountUpdate: processing host jc #661 deltaFile
/var/lib/backuppc/pc/jc/661/refCnt/poolCntDelta_1_0_0_4002 with 86385
entries
BackupPC_refCountUpdate: computing totals for host jc
BackupPC_refCountUpdate: host jc got 0 errors (took 374 secs)
BackupPC_refCountUpdate total errors: 0
Xfer PIDs are now
Finished BackupPC_refCountUpdate (running time: 377 sec)
Xfer PIDs are now
--
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/