emerge sync errors with io.c?

Message

MattSharp · Post by **MattSharp** » Wed Nov 03, 2004 6:09 am

I am getting the error below when I try to emerge sync.

rsync: connection unexpectedly closed (46 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
>>> retry ...

Now before anyone says anything about rsync servers, let me first say that I am using a local rsync server and my other computers are not having any problems.

Based on the io.c file it is some sort of compile problem or something.

I have recompiled my kernel as well as gcc and glibc and rsync. Nothing....

This really sucks.

carpman · Post by **carpman** » Wed Nov 03, 2004 11:00 am

I am getting io.c error but with differnt error code:

Code: Select all

snip
app-sci/
app-text/
app-text/dictd/files/
app-xemacs/
io timeout after 180 seconds - exiting
rsync error: timeout in data send/receive (code 30) at io.c(109)

moocha · Post by **moocha** » Wed Nov 03, 2004 2:19 pm

That's not related to anything you've compiled on your machine (so most probably nothing to with either your kernel, glibc, gcc, or whatever). It simply is an error message from rsync telling you that your connections get dropped. Simply try again, optionally waiting for a better time.

Dr_Stein · Post by **Dr_Stein** » Wed Nov 03, 2004 9:20 pm

receiving file list ...
99146 files to consider

!!! 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)

-----------

Like that?

The connection is a full 100mbit pipe and we're only using 3mbit. There is 0% packet loss. The rsync server is run by a friend of mine, and the pipe it's sitting on is at only 5% utilization.

It is most definately *NOT* a bandwidth/network related problem in my particular case, but the io.c issue is biting me hard.

MattSharp · Post by **MattSharp** » Wed Nov 03, 2004 10:07 pm

moocha wrote:That's not related to anything you've compiled on your machine (so most probably nothing to with either your kernel, glibc, gcc, or whatever). It simply is an error message from rsync telling you that your connections get dropped. Simply try again, optionally waiting for a better time.

Um no you are incorrect. It it NOT just my connection getting dropped. No matter how many times or when I dod it, it does not work. Different RSYNC servers, nothing makes a diference.

MattSharp · Post by **MattSharp** » Wed Nov 03, 2004 11:33 pm

MattSharp wrote:
moocha wrote:That's not related to anything you've compiled on your machine (so most probably nothing to with either your kernel, glibc, gcc, or whatever). It simply is an error message from rsync telling you that your connections get dropped. Simply try again, optionally waiting for a better time.
Um no you are incorrect. It it NOT just my connection getting dropped. No matter how many times or when I dod it, it does not work. Different RSYNC servers, nothing makes a diference.

I take it back. I did not try other RSYNC Servers. I restarted rsync dameon on my server and it worked. Not sure why I had to though. Very odd.

carpman · Post by **carpman** » Thu Nov 04, 2004 10:23 am

Hello, i have tried both:

Code: Select all

SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"

but both fail with same error.

Any ideas?

cheers

suburbanizedgeek · Post by **suburbanizedgeek** » Thu Nov 04, 2004 1:25 pm

I had the same problem. In my case i had some data corruption in my /usr/portage directory. run fsck to check for anything like that. Also you could try deleting /usr/portage/*, as `emerge sync` rebuilds it anyways.

alexerre · Post by **alexerre** » Thu Nov 04, 2004 8:34 pm

I have emerge the new portage version first.
while i'm emerging the prompt said me that i had to do after

Code: Select all

emerge metadata

and then

Code: Select all

emerge sync

Whene the portage was installed I did the command
and the emerge sync return me the io.c error...
Now I try to delete the /usr/portage/* and then
emerge sync

Stay tuned

carpman · Post by **carpman** » Thu Nov 04, 2004 11:17 pm

i tried the delete /usr/portage/* still same error but a reboot seemed to do the trick.

Though on completion of sync it told me i had to update my profile, wonder if this was anything to do with it?

moocha · Post by **moocha** » Thu Nov 04, 2004 11:55 pm

Again, rsync errors related to io.c indicate dropped connections while communicating with the rsync server. A reboot fixing it is most likely because your network adapter's modules were reloaded.

carpman · Post by **carpman** » Fri Nov 05, 2004 4:46 am

moocha wrote:Again, rsync errors related to io.c indicate dropped connections while communicating with the rsync server. A reboot fixing it is most likely because your network adapter's modules were reloaded.

Network card is built into kernel and not as module so would this still be the problem?

BlinkEye · Post by **BlinkEye** » Sat Dec 11, 2004 11:27 pm

i too get systematically the same error. after some (re)tries it usually works. i never had this before ...

JackDog · Post by **JackDog** » Mon Dec 13, 2004 3:44 pm

I can also verify this problem using the e1000 driver for an intel card on a dell box. This has happened on three different networks and still happens when the rsync server is plugged into the same switch.

Its either two things, network driver (kernel driver issue) or a bad compilation somewhere (dep of rsync is screwed). Out of all the boxes I maintain, there are two that do this. Both use the e1000 driver. However they have both been updated at the same time for over a year with the same USE flags. So it could be a compilation issue somewhere as well. I do use different kernels on each of them though; 2.6.9 and 2.6.5.

To sum up:
Its not a proxy issue, its not a firewall issue, its not a network cable issue, its not a solar flare issue, its not a kernel module loading problem, reboots dont fix it, deleting /usr/portage does not fix it, its obvious its a communications issue but there is no working solution yet.

From the rsync ebuild:

Code: Select all

RDEPEND="virtual/libc
        !build? ( >=dev-libs/popt-1.5 )"
DEPEND="${RDEPEND}
        >=sys-apps/sed-4
        acl? ( sys-apps/acl )"

I have recompiled the immediate dependencies with not luck.

Could everyone post their network cards and driver used if you have encountered this problem?

BlinkEye · Post by **BlinkEye** » Mon Dec 13, 2004 5:41 pm

i use the same driver, built in with kernel-2.6.9-nitro2

mattheweast · Post by **mattheweast** » Wed Jan 19, 2005 1:02 am

yeah same problem here... what on earth is going on?!? Here is the error I get, which is sometimes even near the end of the sync:

Code: Select all

rsync error: timeout in data send/receive (code 30) at io.c(153)
rsync: connection unexpectedly closed (5651616 bytes received so far) [receiver]rsync error: error in rsync protocol data stream (code 12) at io.c(359)

This is all over the forums, no solution that I can find!

I've tried MANY rsync servers (uk.gentoo europe.gentoo gentoo us.gentoo etc).

emerge-websync always works afaics. But afterwards, my emerge syncs still generally fail.

My other PC on the same network does not have this problem. I'm using a dlink wireless card on this machine, with the acx111 driver.

M

P.S. Should a bug be filed about this??

BlinkEye · Post by **BlinkEye** » Wed Jan 19, 2005 1:06 am

for me it was a kernel issue. it is gone now

JjcampNR · Post by **JjcampNR** » Wed Jan 19, 2005 5:49 am

This issue is cropping up with a TON of people, in my non-developer opinion it's something that was introduced in one of the last Portage or rsync updates. If you'd like to see the other threads, you can find them here:

http://forums.gentoo.org/viewtopic.php? ... 37#1989637

http://forums.gentoo.org/viewtopic.php? ... 96#1994196

--Josh

bilan · Post by **bilan** » Wed Feb 09, 2005 2:59 pm

Dr_stein said:
It is most definately *NOT* a bandwidth/network related problem in my particular case, but the io.c issue is biting me hard

I cant most agree

I had the same problem and was looking for a solution since a while.
I just found: emerge the new (and masked) 2.6.3 of rsync and the problem is finaly solved !!!

BlinkEye · Post by **BlinkEye** » Wed Feb 09, 2005 3:03 pm

bilan wrote:Dr_stein said:
It is most definately *NOT* a bandwidth/network related problem in my particular case, but the io.c issue is biting me hard

I cant most agree
I had the same problem and was looking for a solution since a while.
I just found: emerge the new (and masked) 2.6.3 of rsync and the problem is finaly solved !!!

forgot to post here - net-misc/rsync-2.6.3 does solve the issue for me too

bocacorazon · Post by **bocacorazon** » Sun Feb 20, 2005 5:11 pm

In my case it was a corrupt file system.

I have an amd64 with SCSI drives and that is trouble by itself...

Since I am just starting to install the system I just reformated the partition, downloaded the portage tar again, extracted it and now sync works...

carpman · Post by **carpman** » Sun Feb 20, 2005 10:19 pm

bocacorazon wrote:In my case it was a corrupt file system.

I have an amd64 with SCSI drives and that is trouble by itself...

Bit off topic but why is amd 64 and scsi trouble?

When i have the time that is going to be a new install for me?

BlinkEye · Post by **BlinkEye** » Tue Feb 22, 2005 7:52 am

well, i have an amd64 and SATA drives. it wasn't an easy setup, but this was due to me starting the installation so very early almost nobody had done it before me and setting up a raid5. it's not that easy, but once you get the clue about grub and the naming of devices you won't have any problems. besides, until now there is much information to be found in the forum.

emerge sync errors with io.c?

emerge sync errors with io.c?

Corrupt filesystem

Re: Corrupt filesystem