rsync - Jul 2005 - [Bug 2783] Random high loads during syncs (server side) / client stream errors

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





------- Additional Comments From samba-mirror@planetmirror.com  2005-07-18 18:08
-------
We at PlanetMirror see this error regularly from our upstream gentoo mirrors, as
well as a plethora of
other upstream mirrors. Personally, while I hope this fix in 2.6.5 resolves the
problems, what you're
suggesting here will make a mammoth task for almost every mirror site on the
planet.

Would it be wise to include sane defaults for both client and server/daemon,
such that simply upgrading
to 2.6.5 dramatically decreases the problem?

-- 
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=2783


pvarner@varnerfamily.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pvarner@varnerfamily.org




------- Additional Comments From pvarner@varnerfamily.org  2005-08-04 07:58
-------
We are seeing this error as well at my workplace.  Both sides are using 2.6.5.
We are invoking rsync with the following command line.

/usr/bin/rsync -e ssh --rsync-path=/usr/bin/rsync -av --recursive --timeout=0
user@host:/path/to/data /path/to/save

The error is occuring on hosts where the server side is under high load from the
application that is running on that host. We are not running an rsync daemon on
the server side.

The latest error is:
Read from remote host hostname: Connection reset by peer
rsync: connection unexpectedly closed (51838271 bytes received so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(434)
rsync: connection unexpectedly closed (34295 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(434)

-- 
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=2783


wayned@samba.org changed:

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




------- Additional Comments From wayned@samba.org  2005-08-04 10:17
-------
> Would it be wise to include sane defaults for both client and server/daemon
Rsync has always had sane defaults for both client and server/daemon: no
timeouts are enabled by default, which means that the connection will continue
as long as both sides are present.  If you set a timeout in the rsyncd.conf
file, I'd recommend that you set it to be quite long -- maybe something like
an
hour -- just so that it cleans up malicious/buggy connections, but does not
interfere with slow transfers.

-- 
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=2783





------- Additional Comments From wayned@samba.org  2005-08-04 10:20
-------
> The latest error is:
> Read from remote host hostname: Connection reset by peer
All this tells you is that the connection closed.  See the issues/debugging
webpage for ways to diagnose what is happening to make the remote end of the
connection go away (assuming that it is not a network issue).

-- 
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.