Version 2.1.2 using rsync.
I have a client that intermittently fails with "aborted by signal=PIPE",
which I realise is a common error. I have $Conf{ClientTimeout} =
72000; the end of the log file (with $Conf{XferLogLevel} = 8;) looks like
this:
--------------------------------------------------------------------------------
Starting file 114944 (), blkCnt=256, blkSize=524288, remainder=503040
: size doesn't match ( vs 134196480)
: blk=255, newData=0, rxMatchBlk=, rxMatchNext=0
: blk=, newData=255, rxMatchBlk=255, rxMatchNext=256
Unable to read 503040 bytes from got=0, seekPosn=133693440 (0,1,256,,)
Read EOF:
Tried again: got 0 bytes
Child is sending done
Got done from child
Can't write 4 bytes to socket
Got stats: 1279724134 1279345231 1096045344 0 ('errorCnt' =>
1,'ExistFileSize' => 0,'ExistFileCnt' => 113057,'TotalFileCnt' =>
113057,'ExistFileCompSize' => 463081472,'TotalFileSize' => 0) finish:
removing in-process file
--------------------------------------------------------------------------------
Does the "Read EOF" suggest a network problem between client and server?
Or is there some other more likely cause?
Thanks,
Keith
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
