BackupPC-users

[BackupPC-users] BackupPC fails with aborted by signal=PIPE, Can't write to socket

2017-01-16 15:14:57
Subject: [BackupPC-users] BackupPC fails with aborted by signal=PIPE, Can't write to socket
From: John Spitzer <johned9999 AT comcast DOT net>
To: backuppc-users AT lists.sourceforge DOT net
Date: Mon, 16 Jan 2017 12:13:55 -0800
I have BackupPC setup with three host configurations to backup three 
separate areas of one system. Two of the hosts configurations are 
working. One repeatedly fails with the messages:

Can't write 33792 bytes to socket
Can't write 35328 bytes to socket
...
Got fatal error during xfer (aborted by signal=PIPE)

I would appreciate help determining why the backups are failing and how 
to keep it from failing again. I also would like help to recover the 
backup archive so that I don't have to delete the entire backup and 
start over.

I am using version 3.3.1, on Ubuntu 14.04. I am backing up over the 
network to a Netgear ReadyNAS 102. When the backup is working I can get 
up to 80 MB/s transfer rate to and from the NAS.

The first time this happened I deleted the entire backup for this host. 
It then works for a few backup cycles but then fails again. The back 
cycles were able to make a full, two incremental, a full, two 
incremental. Then it failed again with these same errors on a full backup.

When the backup failed the first time, I tried to find what file was 
causing the failure by analyzing logs and excluding files. But the file 
the that was being backed up at the time the backup failed changed.

I have set the logging level to 8 to try and capture more data. There is 
the portion of the log for the file that is failing and the previous file:
--------
attribSet: dir=fDrive1/.virtualbox/Machines/Win 10 Pro x64 VM07/Logs exists
attribSet(dir=fDrive1/.virtualbox/Machines/Win 10 Pro x64 VM07/Logs, 
file=VBox.log.1, size=113405, placeholder=)
Starting file 40 (.virtualbox/Machines/Win 10 Pro x64 
VM07/Logs/VBoxStartup.log), blkCnt=255, blkSize=2048, remainder=1713
.virtualbox/Machines/Win 10 Pro x64 VM07/Logs/VBoxStartup.log: blk=, 
newData=, rxMatchBlk=0, rxMatchNext=255
MD4 
/media/Backup/BackupPC/pc/johned-linux-vbox/5/fDrive1/f.virtualbox/fMachines/fWin
 
10 Pro x64 VM07/fLogs/fVBoxStartup.log cache = , invalid =
.virtualbox/Machines/Win 10 Pro x64 VM07/Logs/VBoxStartup.log got exact 
match
.virtualbox/Machines/Win 10 Pro x64 VM07/Logs/VBoxStartup.log got 
digests 6b8d347f24fcac7a460fdfc49badc3a8 vs 6b8d347f24fcac7a460fdfc49badc3a8
.virtualbox/Machines/Win 10 Pro x64 VM07/Logs/VBoxStartup.log: nothing to do
   same     664 1000/1000      521905 .virtualbox/Machines/Win 10 Pro 
x64 VM07/Logs/VBoxStartup.log
attribSet: dir=fDrive1/.virtualbox/Machines/Win 10 Pro x64 VM07/Logs exists
attribSet(dir=fDrive1/.virtualbox/Machines/Win 10 Pro x64 VM07/Logs, 
file=VBoxStartup.log, size=521905, placeholder=)
Starting file 41 (.virtualbox/Machines/Win 10 Pro x64 VM07/Win 10 Pro 
x64 VM07-disk1.vdi), blkCnt=3068608, blkSize=16384, remainder=16384
/media/Backup/BackupPC/pc/johned-linux-vbox/5/fDrive1/f.virtualbox/fMachines/fWin
 
7 Pro VM04/fSnapshots/f{e32c1bb2-0ca4-44cc-b858-7d17d92789a4}.vdi cache 
= , invalid = , phase = 0
Sending csums for .virtualbox/Machines/Win 7 Pro 
VM04/Snapshots/{e32c1bb2-0ca4-44cc-b858-7d17d92789a4}.vdi (size=18785239040)
.virtualbox/Machines/Win 10 Pro x64 VM07/Win 10 Pro x64 VM07-disk1.vdi: 
blk=, newData=, rxMatchBlk=0, rxMatchNext=3068608
MD4 
/media/Backup/BackupPC/pc/johned-linux-vbox/5/fDrive1/f.virtualbox/fMachines/fWin
 
10 Pro x64 VM07/fWin 10 Pro x64 VM07-disk1.vdi cache = , invalid =
Can't write 33792 bytes to socket
Can't write 35328 bytes to socket
Sending csums, cnt = 138, phase = 1
/media/Backup/BackupPC/pc/johned-linux-vbox/5/fDrive1/f.virtualbox/fMachines/fWin
 
7 Pro VM04/fWin 7 Pro VM04.vbox cache = , invalid = , phase = 1
Sending csums for .virtualbox/Machines/Win 7 Pro VM04/Win 7 Pro 
VM04.vbox (size=33258)
Done: 0 files, 0 bytes
Got fatal error during xfer (aborted by signal=PIPE)
Backup aborted by user signal
Not saving this as a partial backup since it has fewer files than the 
prior one (got 0 and 0 files versus 16)

Thank you for your help.

John S.

P.S. I'm new to posting to SourceForge, so forgive me if my format is 
not up to snuff.

------------------------------------------------------------------------------
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 AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

<Prev in Thread] Current Thread [Next in Thread>