On Sun, Nov 02, 2008 at 03:13:10AM -0500, Ricky Zhou wrote:
On 2008-11-02 08:00:02 AM, Cron Daemon wrote:
rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(614) [receiver=2.6.8]
Could these be due to the recent rsync rate limiting changes? Should we make them only affect secondary1, perhaps?
perhaps... though there aren't so many proxy* servers (are there) that they'd be seen as being >10, or >2 from a single IP?
in fact, yes, >2 per IP. My guess is it's multiple syncFiles.sh running in parallel cronjobs simultaneously.
I'll drop that bit for now.
On Sun, Nov 02, 2008 at 11:57:27AM -0600, Matt Domsch wrote:
On Sun, Nov 02, 2008 at 03:13:10AM -0500, Ricky Zhou wrote:
On 2008-11-02 08:00:02 AM, Cron Daemon wrote:
rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(614) [receiver=2.6.8]
Could these be due to the recent rsync rate limiting changes? Should we make them only affect secondary1, perhaps?
perhaps... though there aren't so many proxy* servers (are there) that they'd be seen as being >10, or >2 from a single IP?
in fact, yes, >2 per IP. My guess is it's multiple syncFiles.sh running in parallel cronjobs simultaneously.
I'll drop that bit for now.
I've reverted the rsync.xinetd file used on puppet1 and elsewhere back to its original state which doesn't rate-limit. As suggested, I created rsync.xinetd.secondary which does rate limiting, and enabled such for secondary1.
Thanks, Matt
infrastructure@lists.fedoraproject.org
-
Matt Domsch