rsync - Jul 2006 - DO NOT REPLY [Bug 3979] New: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe

https://bugzilla.samba.org/show_bug.cgi?id=3979

           Summary: writefd_unbuffered failed to write 4092 bytes phase
                    send_file_entry broken pipe
           Product: rsync
           Version: 2.6.8
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: tvcn15100@tvcablenet.be
         QAContact: rsync-qa@samba.org


I reopen this bug 1959 as the same problem occurs now on my server after month
of clean operation...same message with v2.6.8 of rsync on both servers.
Rsync works fine on A->A and B->B but any sync from A->B hangs.
I tried all the solution of bug 1959 followup....nothing works.

Help appreciated.

Regards,

Chris

+++ This bug was initially created as a clone of Bug #1959 +++

we are doing rsync from server A -> B and A->C. 

A, C are running on Linux 2.4.9-e-34 and B is running on Linux 2.4.9-e-38

the following rsync command works just fine from A->B:

rsync --exclude-from /local/dba/scripts/shoprod1_exclude_applfiles.txt -rlvz -e
ssh /prod/applmgr/1159/ applprod@twnprod1:/prod/applmgr/1159/

the "same" command doesnt work from A->C:

the following rsync command works just fine from A->B:

rsync --exclude-from /local/dba/scripts/shoprod1_exclude_applfiles.txt -rlvz -e
ssh /prod/applmgr/1159/ applprod@twnprod2:/prod/applmgr/1159/

we get the followin error at different stages, e.g. build stage or after
processing a few files:

rsync: writefd_unbuffered failed to write 4092 bytes: phase
"send_file_name":
broken Pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(836)

we are using rsync2.6.2 protocol version 28.

Im at a loss to understand why this is happening.

I already tried -vv option -> same error comes after processing some files
from
the exclusion file

If I use the -vvv option, it hangs on a particular command like this on server
A:

[sender] make_file(per/11.5.0/help/US/puploadw.htm,*,2)
[sender] make_file(per/11.5.0/help/US/puplorgd.htm,*,2)
--> this is where it hangs..

doing a strace on the rsync process on server A shows :

select(5,NULL, [4], NULL, {16,970000}) = 0 (Timeout)
select(5,NULL, [4], NULL, {60, 0}) = 0 (Timeout)
select(5,NULL, [4], NULL, {60, 0}) = 0 (Timeout)
..

strace on rsync process on server C shows:

select(2,NULL, [1], NULL, {29,290000}) = 0 (Timeout)
select(2,NULL, [1], NULL, {60, 0}) = 0 (Timeout)
select(2,NULL, [1], NULL, {60, 0}) = 0 (Timeout)
..

and so it hangs.. without doing anything..


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=3979


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from wayned@samba.org  2006-09-17 18:39 MST -------
Your bug report is contradictory: at one spot it says you're using 2.6.8, at
another 2.6.2.  Please follow the procedures for debugging why the remote rsync
is going away (see the Issues and Debuggin webpage) and cite any system-call
tracing and netstat output for a hang (be sure to get both processes from the
receiving side when pushing files).


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=3979


ttimo@ttimo.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|ttimo@ttimo.net             |




------- Comment #2 from ttimo@ttimo.net  2006-09-17 18:43 MST -------
fwiw we fixed our similar case of report this by using a Linux rsync server
instead of cygwin ( TTimo - removing myself from CC )


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=3979


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #3 from wayned@samba.org  2006-10-15 11:29 MST -------
Closing due to lack of response.  Feel free to add more information to this bug
should the problem recur.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.