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

2018-01-29 Thread RAKOTONDRAINIBE Harimino Lalatiana 
Hi Graig,

Nothing happen after I run the command, I will open a new thread then to
avoid confusion.

Thank you

Regards,

Hari

2018-01-27 20:27 GMT+03:00 Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net>:

> 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

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

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

2018-01-26 Thread RAKOTONDRAINIBE Harimino Lalatiana 
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
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-24 Thread 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/

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

2018-01-21 Thread 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




On Sun, Jan 21, 2018 at 2:28 PM, Joel Uckelman  wrote:

> Thus spake Michael Stowe:
> > >
> > > Can anyone suggest what's causing the backup to fail or how I could
> > > further troubleshoot?
> >
> > Certainly.
> >
> > First, to further troubleshoot:  check the logs for rsync on the other
> > side (the system that is being backed up) which may include more
> > information on the fatal errors.
>
> Where would I find logs for rsync on the target system? I see nothing
> which looks relevant in /var/log there.
>
> To be clear, the target system is not running rsyncd. The XferMethod in
> use is "rsync", which I understood was using rsync over ssh.
>
> > Second, suggestions on what's causing the backup to fail:  you haven't
> > specified how the backups are structured, but it certainly looks like
> > rsync backing up files either directly from or mounted from a Windows
> > system.  Some of the non-fatal errors are indicating that you are (for
> > some reason) backing up Internet Explorer cache files.  While a bit
> > silly, this isn't itself a problem, but it strongly implies possible
> > indiscretion with regards to attempting to back up forbidden files
> > (e.g., open or protected without shadow copies) or those whose filenames
> > can't be handled by rsync.
>
> Those files are from a backup of the last Windows system the owner of
> the laptop used, some years prior. The target system is Fedora 26, not
> Windows.
>
> Those Windows files were backed up successfully by BackupPC 3, from the
> user's previous laptop. Unfortunately, I upgraded to 4.1.5 in the same
> week when the user got a new lapop, so I never had a chance to see how
> the old BackupPC version behaved with the new laptop.
>
> --
> 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-21 Thread Joel Uckelman 
Thus spake Michael Stowe:
> > 
> > Can anyone suggest what's causing the backup to fail or how I could
> > further troubleshoot?
> 
> Certainly.
> 
> First, to further troubleshoot:  check the logs for rsync on the other 
> side (the system that is being backed up) which may include more 
> information on the fatal errors.

Where would I find logs for rsync on the target system? I see nothing
which looks relevant in /var/log there.

To be clear, the target system is not running rsyncd. The XferMethod in
use is "rsync", which I understood was using rsync over ssh.
 
> Second, suggestions on what's causing the backup to fail:  you haven't 
> specified how the backups are structured, but it certainly looks like 
> rsync backing up files either directly from or mounted from a Windows 
> system.  Some of the non-fatal errors are indicating that you are (for 
> some reason) backing up Internet Explorer cache files.  While a bit 
> silly, this isn't itself a problem, but it strongly implies possible 
> indiscretion with regards to attempting to back up forbidden files 
> (e.g., open or protected without shadow copies) or those whose filenames 
> can't be handled by rsync.

Those files are from a backup of the last Windows system the owner of
the laptop used, some years prior. The target system is Fedora 26, not
Windows. 

Those Windows files were backed up successfully by BackupPC 3, from the
user's previous laptop. Unfortunately, I upgraded to 4.1.5 in the same
week when the user got a new lapop, so I never had a chance to see how
the old BackupPC version behaved with the new laptop.

-- 
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/

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

2018-01-20 Thread Joel Uckelman 
I've been unable to back up one of my systems for the past several months
and am out of ideas for troubleshooting it. I have BackupPC 4.1.5 running
on a Fedora 26 system. It successfully backs up five other systems, so
I am apparently not having a general problem with BackupPC on my backup
server.

This is what I see in the LOG file for the failing host after I attempt
triggering a backup manually:

2018-01-21 00:28:38 Renaming /var/lib/BackupPC//pc/athena/XferLOG.687.z -> 
/var/lib/BackupPC//pc/athena/XferLOG.687.z.tmp
2018-01-21 00:28:39 full backup started for directory /
2018-01-21 00:40:39 Got fatal error during xfer (No files dumped for share /)
2018-01-21 00:40:44 Backup aborted (No files dumped for share /)

In Errors, under Xfer Error Summary, I see this:

XferLOG file /var/lib/BackupPC//pc/athena/XferLOG.687.z created 2018-01-21 
00:28:39 
Backup prep: type = full, case = 6, inPlace = 1, doDuplicate = 0, newBkupNum = 
687, newBkupIdx = 10, lastBkupNum = , lastBkupIdx =  (FillCycle = 0, noFillCnt 
= 1)
Running: /usr/bin/rsync_bpc --bpc-top-dir /var/lib/BackupPC/ --bpc-host-name 
athena --bpc-share-name / --bpc-bkup-num 687 --bpc-bkup-comp 3 
--bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 375732 
--bpc-attrib-new --bpc-log-level 1 -e /usr/bin/ssh\ -l\ root 
--rsync-path=/usr/bin/rsync --super --recursive --protect-args --numeric-ids 
--perms --owner --group -D --times --links --hard-links --delete 
--delete-excluded --one-file-system --partial --log-format=log:\ %o\ %i\ %B\ 
%8U,%8G\ %9l\ %f%L --stats --checksum --timeout=72000 --include=/etc 
--include=/var --include=/home --include=/boot --include=/boot/grub 
--include=/boot/grub/grub.conf --include=/root --exclude=/\* --exclude=/boot/\* 
--exclude=/boot/grub/\* --exclude=/var/cache --exclude=/var/lock 
--exclude=/var/run --exclude=/home/uckelman/.gvfs --exclude=/home/liana/.gvfs 
athena:/ /
full backup started for directory /
Xfer PIDs are now 29288
This is the rsync child about to exec /usr/bin/rsync_bpc
Xfer PIDs are now 29288,29290
xferPids 29288,29290
G bpc_fileOpen: can't open file 
/var/lib/BackupPC//pc/athena/687/f%2f/fhome/fliana/f.cache/fksycoca5 (from 
home/liana/.cache/ksycoca5, 3, 0, 0)
rsync_bpc: failed to open "/home/liana/.cache/ksycoca5", continuing: No such 
file or directory (2)
[ skipped 113 lines ]
file has vanished: "/home/liana/.local/share/gvfs-metadata/home-541c997f.log"
[ skipped 53 lines ]
file has vanished: 
"/home/liana/windows/AppData/Local/Microsoft/Windows/Temporary Internet 
Files/Content.IE5/2TJ3MKOV/=ns-97887206_1251557233,1138a6119b01da5,IT_Enterprise_Exchange,;;kw=;dcopt=ist;tile=1;ord1=830214;sz=728x90;contx=IT_Enterprise_Exchange;btg=;ord=1073363542692100[1]"
IO error encountered -- skipping file deletion
R bpc_fileOpen: can't open file 
/var/lib/BackupPC//pc/athena/687/f%2f/fhome/fliana/fwindows/fAppData/fLocal/fMicrosoft/fWindows/fTemporary
 Internet 
Files/fContent.IE5/f2TJ3MKOV/f=ns-97887206_1251557233,1138a6119b01da5,IT_Enterprise_Exchange,;;kw=;dcopt=ist;tile=1;ord1=830214;sz=728x90;contx=IT_Enterprise_Exchange;btg=;ord=1073363542692100[1]
 (from home/liana/windows/AppData/Local/Microsoft/Windows/Temporary Internet 
Files/Content.IE5/2TJ3MKOV/=ns-97887206_1251557233,1138a6119b01da5,IT_Enterprise_Exchange,;;kw=;dcopt=ist;tile=1;ord1=830214;sz=728x90;contx=IT_Enterprise_Exchange;btg=;ord=1073363542692100[1],
 3, 0, 0)
[ skipped 248 lines ]
rsync_bpc: writefd_unbuffered failed to write 308 bytes to message fd 
[receiver]: Broken pipe (32)
Done: 1 errors, 8 filesExist, 48913 sizeExist, 18388 sizeExistComp, 0 
filesTotal, 0 sizeTotal, 46 filesNew, 63072075 sizeNew, 15060567 sizeNewComp, 
375787 inode
rsync error: error in rsync protocol data stream (code 12) at io.c(1556) 
[receiver=3.0.9.11]
rsync_bpc exited with fatal status 0 (139) (rsync error: error in rsync 
protocol data stream (code 12) at io.c(1556) [receiver=3.0.9.11])
[ skipped 32 lines ]
Xfer PIDs are now 
Got fatal error during xfer (No files dumped for share /)
Backup aborted (No files dumped for share /)
BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 6, inPlace = 1, 
lastBkupNum = 
BackupFailCleanup: inPlace with no new files... no cleanup
Running BackupPC_refCountUpdate -h athena -f on athena
Xfer PIDs are now 29364
BackupPC_refCountUpdate: athena #687 inodeLast set to 378393 (was 375731)
BackupPC_refCountUpdate: host athena got 0 errors (took 35 secs)
Xfer PIDs are now 
Finished BackupPC_refCountUpdate (running time: 35 sec)
Xfer PIDs are now 


Can anyone suggest what's causing the backup to fail or how I could
further troubleshoot?

-- 
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: