Hi Guilherme On 26.05.2014 15:57, Guilherme Cunha wrote: > Hi, > > Full lines about this: " > > Can't write 32780 bytes to socket > > Read EOF: >
The real error message probably is above the lines you quoted. I guess it is something like: Remote[1]: rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3] This means that the rsync server did not send any data for the time specified in the timeout value in /etc/rscynd,conf to the backuppc client. This can happen due to large deltas, complex settings, a busy client or a couple o other reasons. If I where you, I'd double the "timeout" value in the /etc/rsyncd.conf of the system you want to backup. If this does not help, run a fsck on the system to backup because file system problems on the system to backup will cause the rsyncd server to be unable to respond the the request from the server. With kind regards Stefan Peter -- "In summary, I think you are trying to solve a problem that may not need to be solved, using a tool that is not meant to solve it, without understanding what is causing your problems and without knowing how the tool actually works in the first place :)" Jeffrey J. Kosowsky on the backuppc mailing list
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
_______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
