From: Sarah J. Blake <sarah@gr...> - 2005-04-06 17:03:09
I'm getting this error after rsync has been going for a while. Any idea what
it means? Should I just keep trying until it's done?
rsync: read error: Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at io.c(201)
rsync: connection unexpectedly closed (2523566 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
!!! Rsync has not successfully finished. It is recommended that you keep
!!! trying or that you use the 'emerge-webrsync' option if you are unable
!!! to use rsync due to firewall or other restrictions. This should be a
!!! temporary problem unless complications exist with your network
!!! (and possibly your system's filesystem) configuration.
Sarah J. Blake
From: Thomas Reitmayr <treitmayr@ya...> - 2005-04-10 19:22:36
I just had the same problem when building a new coLinux/Gentoo system. For
me it was just a memory issue - I forgot to enable some swap space before
running "emerge sync" and right at the point you describe it puked. Take a
look at the windows console from where coLinux was started up, and if you
see a message saying that rsync was killed due to insufficient memory,
then you might have forgotten to mount your swap file/partition, too.
Gesendet von Yahoo! Mail - Jetzt mit 250MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
From: Sarah J. Blake <sarah@gr...> - 2005-04-10 20:12:36
Actually I think the problem was my router. I didn't think about it--I read
"if you are behind a firewall" and forgot that my router is acting as a
firewall. I ran emerge -webrsync with no problem and then continued on
through the emerge and update steps with no further trouble.
Still learning but making progress...
Sarah J. Blake