Rsync 2.6.8

Lakshminarayanan Radhakrishan lradhakr at
Wed Oct 4 11:39:05 GMT 2006


I am facing the same following error, eventhough the remote site is not 
down. Because both ACTIVE and STBY
sites are with me only.

" 2006/10/05 17:51:53 [1617] rsync: writefd_unbuffered failed to write 
83 bytes [generator]: Broken pipe (32)
  2006/10/05 17:51:53 [1617] rsync error: error in rsync protocol data 
stream (code 12) at io.c(1119) [generator=2.6.8]"

I am not getting  tag-3 problem patch you mentioned in your mail.  Today 
also i downloaded the following latest rsync 2.6.8
packages from

 465783 Oct  4 15:20    libgcc-3.4.6-sol10-sparc-local.gz
279773 Oct  4 15:20     rsync-2.6.8-sol10-sparc-local.gz
1416932 Oct  4 15:20   libiconv-1.9.2-sol10-sparc-local.gz

thanks & regards

Wayne Davison wrote:

>On Wed, Sep 27, 2006 at 02:13:01PM +0530, Lakshminarayanan Radhakrishan wrote:
>>2006/09/21 02:04:31 [4513] rsync: writefd_unbuffered failed to write 
>>4092 bytes [generator]: Broken pipe (32)
>As the Issues and Debugging webpage says, this error just indicates that
>the remote side went away.  Why did it go away?  The cited webpage gives
>you some ideas on what you can do to figure it out.
>Also, if you're pushing data to a daemon, be sure you've applied the fix
>for the tag-3 problem (or are using a version that has this patched).
-------------- next part --------------
HTML attachment scrubbed and removed

More information about the rsync mailing list