Re: [BackupPC-users] backup failing with "No files dumped for share /"

2018-01-27 Thread Craig Barratt via BackupPC-users 
Joel,

Thanks for confirming.  Those errors shouldn't appear on the next full
backup.

I just released rsync-bpc-3.0.9.12 with that fix.

Craig

On Wed, Jan 24, 2018 at 3:16 AM, Joel Uckelman  wrote:

> Thus spake Craig Barratt via BackupPC-users:
> > Joel,
> >
> > It's hard to tell from the log.  However, one thing worth trying is to
> > build rsync-bpc 3.0.9 from current git, since there was a bug I fixed
> last
> > week that could be related to this:
> >
> > mkdir somewhere
> > cd somewhere
> > git clone https://github.com/backuppc/rsync-bpc
> > cd rsync-bpc
> > git checkout 3.0.9
> >
> > ./configure
> >
> > make
> >
> > Then set $Conf{RsyncBackupPCPath} to the new rysnc_bpc executable (ie:
> > /path/to/somewhere/rsync-bpc/rsync_bpc) and try running the backup
> again.
> >
> > If that still fails, the next steps are to increase XferLogLevel (eg, to
> 5
> > or 6), and add -vv to RsyncArgsExtra and send the log file.
> >
> > Craig
> >
>
> I had a complete successful backup with the patched rsync-bpc. I get
> a bunch of these (~50) in the log now:
>
> G bpc_read: read past EOF; readSize = 262101, posn = 43, fileSize = 43,
> bufferSize = 8388608
> G bpc_read: read past EOF; readSize = 262144, posn = 262144, fileSize =
> 43, bufferSize = 8388608
> G bpc_read: read past EOF; readSize = 262144, posn = 524288, fileSize =
> 43, bufferSize = 8388608
>
> But the backup appears to have been successful. Thanks!
>
> --
> J.
>
> 
> --
> 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/
>
--
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/

Re: [BackupPC-users] backup failing with "No files dumped for share /"

2018-01-27 Thread Craig Barratt via BackupPC-users 
Hari,

This doesn't look related to the original thread.  For some reason
rsync_bpc's connection to the client is closed before any files get
transferred.

What happens when you run this comment as the backuppc user:

/usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync

Craig

On Fri, Jan 26, 2018 at 5:01 AM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi everyone,
>
> I encounter the same issue now when I backup my localhost. I had a problem
> after an OS upgrade and after some change and an upgrade in 4.1.4, the
> issue has been resolved for all the hosts except for my localhost.
>
> I already tried all that was said earlier in the forum by  building
> rsync-bpc with the current git and increasing the xferlog
>
> The error in xferlog :
>
> This is the rsync child about to exec 
> /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
> opening connection using: /usr/bin/ssh -q -x -l backuppc localhost 
> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
> protected args: --timeout=72000 --numeric-ids . /
> rsync_bpc: connection unexpectedly closed (0 bytes received so far) [Receiver]
> bpc_sysCall_cleanup: doneInit = 1
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 530710 inode
> Parsing done: nFilesTotal = 0
> rsync error: error in rsync protocol data stream (code 12) at io.c(629) 
> [Receiver=3.0.9.11]
> 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.11])
> Xfer PIDs are now
> Executing DumpPostUserCmd: /var/db/BackupPC/mailadmin.sh 0 localhost
> Got fatal error during xfer (rsync error: error in rsync protocol data stream 
> (code 12) at io.c(629) [Receiver=3.0.9.11])
> Backup aborted (rsync error: error in rsync protocol data stream (code 12) at 
> io.c(629) [Receiver=3.0.9.11])
> BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace = 1, 
> lastBkupNum =
> BackupFailCleanup: inPlace with no new files... no cleanup
> Running BackupPC_refCountUpdate -h localhost -f on localhost
> Xfer PIDs are now 17115
> BackupPC_refCountUpdate: host localhost #153: gotFsck = 1, gotDelta = , 
> gotPoolCnt = 1, gotNoPoolCntOk =
> BackupPC_refCountUpdate: processing host localhost #153 (fsck = 1)
> BackupPC_refCountUpdate: processing host localhost #153 deltaFile 
> /var/db/BackupPC/pc/localhost/153/refCnt/poolCntDelta_0_0_0_17115 with 510160 
> entries
> BackupPC_refCountUpdate: computing totals for host localhost
> BackupPC_refCountUpdate: host localhost got 0 errors (took 5 secs)
> BackupPC_refCountUpdate total errors: 0
> Xfer PIDs are now
> Finished BackupPC_refCountUpdate (running time: 5 sec)
> Xfer PIDs are now
>
> As I understand it's a problem with rsync-bpc but I didn't find any solution 
> to resolve it.
>
> Thank you,
>
> Hari
>
>
>
>
> 2018-01-24 14:16 GMT+03:00 Joel Uckelman :
>
>> Thus spake Craig Barratt via BackupPC-users:
>> > Joel,
>> >
>> > It's hard to tell from the log.  However, one thing worth trying is to
>> > build rsync-bpc 3.0.9 from current git, since there was a bug I fixed
>> last
>> > week that could be related to this:
>> >
>> > mkdir somewhere
>> > cd somewhere
>> > git clone https://github.com/backuppc/rsync-bpc
>> > cd rsync-bpc
>> > git checkout 3.0.9
>> >
>> > ./configure
>> >
>> > make
>> >
>> > Then set $Conf{RsyncBackupPCPath} to the new rysnc_bpc executable (ie:
>> > /path/to/somewhere/rsync-bpc/rsync_bpc) and try running the backup
>> again.
>> >
>> > If that still fails, the next steps are to increase XferLogLevel (eg,
>> to 5
>> > or 6), and add -vv to RsyncArgsExtra and send the log file.
>> >
>> > Craig
>> >
>>
>> I had a complete successful backup with the patched rsync-bpc. I get
>> a bunch of these (~50) in the log now:
>>
>> G bpc_read: read past EOF; readSize = 262101, posn = 43, fileSize = 43,
>> bufferSize = 8388608
>> G bpc_read: read past EOF; readSize = 262144, posn = 262144, fileSize =
>> 43, bufferSize = 8388608
>> G bpc_read: read past EOF; readSize = 262144, posn = 524288, fileSize =
>> 43, bufferSize = 8388608
>>
>> But the backup appears to have been successful. Thanks!
>>
>> --
>> J.
>>
>> 
>> --
>> 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/
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most