I try: rsync -auv rsync://mirrors.kernel.org/centos/5.2/updates/i386 ..... And get 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] And then, if I keep trying, eventually rsync 'works' and I get my updates. What is causing this?
On Thu, 2008-11-27 at 08:13 -0500, Robert Moskowitz wrote:> I try: > > rsync -auv rsync://mirrors.kernel.org/centos/5.2/updates/i386 ..... > > And get > > 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] > > > And then, if I keep trying, eventually rsync 'works' and I get my updates. > > What is causing this?The server. Ask the sysadmin of kernel.org. -- Ignacio Vazquez-Abrams <ivazqueznet at gmail.com> PLEASE don't CC me; I'm already subscribed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <lists.centos.org/pipermail/centos/attachments/20081127/5d5d131b/attachment-0003.sig>
Robert Moskowitz wrote:> I try: > > rsync -auv rsync://mirrors.kernel.org/centos/5.2/updates/i386 ..... > > And get > > 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] > > > And then, if I keep trying, eventually rsync 'works' and I get my > updates. > > What is causing this?I periodically get this, I chalk it up to rsync not recovering very well from lost packets on the public internet
John R Pierce wrote:> Robert Moskowitz wrote: >> I try: >> >> rsync -auv rsync://mirrors.kernel.org/centos/5.2/updates/i386 ..... >> >> And get >> >> 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] >> >> >> And then, if I keep trying, eventually rsync 'works' and I get my >> updates. >> >> What is causing this? > > > I periodically get this, I chalk it up to rsync not recovering very > well from lost packets on the public internetIt always seems to come at the start of rsync. Don't recall ever seeing it once the files start moving.