!!! 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.
www jnichols # io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(109) io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(109) io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(109) io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(109)
www jnichols #
Ok, so I try emerge-webrsync. It fails too!!
app-xemacs/clearcase/files/ app-xemacs/clearcase/files/digest-clearcase-1.04 68 100% 0.00kB/s 0:00:00 app-xemacs/cookie/ rsync: connection unexpectedly closed (245428 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) cleaning up transferring metadata/cache skipping sync
*** Completed websync, please now perform a normal rsync if possible. Update is current as of the of YYYYMMDD: 20041030
www jnichols #
This is really starting to bother me. I cannot update several machines now. :(
Has ANYONE seen this?
Neither of these machines is low on drive space. I have not seen anythying on Google about this (yes, just to placate those that say "google it" to everything, I actually did Google for it. :P)
Nothing related on bugs.gentoo.org
There's stuff on the forums, tho, but no solutions
Am 31. Okt 2004 um 21:28 Uhr schrieb Jonathan Nichols:
> rsync error: timeout in data send/receive (code 30) at io.c(109) > io timeout after 180 seconds - exiting
This is likely caused by the server. Which server(s) are you using?
> rsync: connection unexpectedly closed (245428 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(189)
If this happens during a local rsync, it could mean that your filesystems are corrupted. Did you check them recently? What kind of filesystem do you use?
On Mon, 1 Nov 2004 17:24:05 +0100, Sebastian Flothow wrote: > > rsync: connection unexpectedly closed (245428 bytes read so far) > > rsync error: error in rsync protocol data stream (code 12) at > > io.c(189)
> If this happens during a local rsync, it could mean that your > filesystems are corrupted. Did you check them recently? What kind of > filesystem do you use?
Isn't error 12 caused by a lack of space? How full is the filesystem containing /usr/portage?
>>If this happens during a local rsync, it could mean that your >>filesystems are corrupted. Did you check them recently? What kind of >>filesystem do you use?
ReiserFS on all of the machines. I ran reiser's fsck on one of the affected boxes, still no luck.
> Isn't error 12 caused by a lack of space? How full is the filesystem > containing /usr/portage?
All 3 boxes are in geographically different locations. 1)PII/450 in Fairfield, California on an SBC ATM circuit 2)Athlon XP 2000 in Pleasant Hill, California on a Speakeasy T1 3)AMD Duron 900 in San Francisco, California on a 100mbit XO ethernet feed.
None of the boxes are running low on disk space. It's really confusing the heck out of me. :(
> All 3 boxes are in geographically different locations. > 1)PII/450 in Fairfield, California on an SBC ATM circuit > 2)Athlon XP 2000 in Pleasant Hill, California on a Speakeasy T1 > 3)AMD Duron 900 in San Francisco, California on a 100mbit XO ethernet feed.
IIRC - if you do a tracepath (or traceroute) on the Speakeasy and XO links, and I suspect the SBC link, they all end up going through the same backbone connection.
On Mon, 01 Nov 2004 16:50:14 -0800, Jonathan Nichols <jnich...@pbp.net> wrote:
> > IIRC - if you do a tracepath (or traceroute) on the Speakeasy and XO links, > > and I suspect the SBC link, they all end up going through the same backbone > > connection.
> > But, as they are failing for some reason, try -
> > If you see any "* * *" with no resolution, there is a dead path or > > node that's blackholing your request.
> > FWIW - my sync through Speakeay in San Jose, CA worked fine on Saturday.
> > It might, if you haven't already, be useful to verify the entries in > > your /etc/resolv.conf on each system.
> I've been able to pretty much rule out the network. They're on vastly > different networks. Traceroutes all complete successfully. A few of the > machines that *do* work are on the same networks... but only a select > few machines cannot emerge sync anymore. :(
> DNS is fully functional. They're not out of disk space. They're not out > of bandwidth either.
