Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
rsync keeps failing in io.c: rsync error: error in rsync pro
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
regaleali
n00b
n00b


Joined: 14 Jan 2005
Posts: 31
Location: Switzerland

PostPosted: Mon Mar 07, 2005 9:03 pm    Post subject: rsync keeps failing in io.c: rsync error: error in rsync pro Reply with quote

Hi all

I've got a fresh install on a Palmax PD1000 (or 1100?, I've long lost the manuals). This is a subnotebook with a Cyrix MediaGXtm MMXtm processor at 266Mhz, 64 MB RAM and a 6GB HD. (The Cyrix is actually a all-in-one CPU/Graphics/Sound processor).
I'm actually running kernel 2.6.10, but the problem also occurred with the install kernel (2.4.something).

Whenever I run emerge --sync, I get errors, first 180 seconds after the download of the ebuilds starts:

receiving file list ...
113454 files to consider
./
app-admin/
[...]
games-action/
io timeout after 180 seconds - exiting
rsync error: timeout in data send/receive (code 30) at io.c(109)
games-arcade/
[...]
kde-base/kdebase/files/
rsync: connection unexpectedly closed (2587288 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)


The above repeats itself with any RSYNC server I specify.
The first error, as said, happens 180 seconds after the start, the second one always when about 2.5 MB were read (differs around 0.1MB from run to run).

This IS a slow machine, admitted, and it's only got a 10Mb pcmcia NIC, but can that have such an influence?
BTW other (faster) machines on the same LAN/WAN link sync without errors.
Network connectivity is always present (ping).

I would like to try and set RSYNC_TIMEOUT to a higher value and to turn compression off (found some google entries about that).
But I can't figure out how to set those values! Somewhere in /etc/portage?

Does anybody have a hint for a lost soul on either the problem or the config stuff?

thx /markus
Back to top
View user's profile Send private message
regaleali
n00b
n00b


Joined: 14 Jan 2005
Posts: 31
Location: Switzerland

PostPosted: Mon Mar 07, 2005 10:37 pm    Post subject: Reply with quote

OK, setting RSYNC_TIMEOUT to 500 in /etc/make.conf helped.
I'm not deleting the entry because the handbook seems to suggest increasing this value if you have a slow connection, not if you have a terribly slow machine ;-)
Back to top
View user's profile Send private message
ilikelinux
n00b
n00b


Joined: 19 Dec 2003
Posts: 50

PostPosted: Sun Jul 17, 2005 1:15 am    Post subject: Reply with quote

Thanks, That helped my problems as well.
Back to top
View user's profile Send private message
kristoczaj
Apprentice
Apprentice


Joined: 18 Apr 2004
Posts: 201
Location: Poland

PostPosted: Wed Oct 19, 2005 8:04 am    Post subject: Reply with quote

same problem,
RSYNC_TIMEOUT=500 in make.conf
helped for me too..
thanks!
Back to top
View user's profile Send private message
pianosaurus
l33t
l33t


Joined: 19 Apr 2004
Posts: 943
Location: Bash$

PostPosted: Sat Oct 22, 2005 5:47 pm    Post subject: Reply with quote

Hmm. This must be a bug. I just got this for the first time on my computer too, and I have a 100 Mbit/s connection. My internet-connection is actually faster than my harddrive. And it's an XP 2100+. Oh well, gonna try to adjust the timeout.
_________________
PKA Cuber
Please add [SOLVED] to the subject of your original post when you feel that your problem is resolved.
Adopt an unanswered post
Back to top
View user's profile Send private message
pianosaurus
l33t
l33t


Joined: 19 Apr 2004
Posts: 943
Location: Bash$

PostPosted: Sat Oct 22, 2005 5:52 pm    Post subject: Reply with quote

Oops, I had a syntax error in my make.conf. Seems it used a timeout of thirty-something seconds, which was fine until recently. I guess portage has grown. But I still think it's a little strange that emerge sync times out even when it's obviously doing something and the connection is fine. Shouldn't this be a "no contact"-timeout?
_________________
PKA Cuber
Please add [SOLVED] to the subject of your original post when you feel that your problem is resolved.
Adopt an unanswered post


Last edited by pianosaurus on Tue Nov 22, 2005 8:40 pm; edited 1 time in total
Back to top
View user's profile Send private message
natanoj
n00b
n00b


Joined: 16 Oct 2004
Posts: 15

PostPosted: Thu Oct 27, 2005 7:07 am    Post subject: Reply with quote

RSYNC_TIMEOUT=500 seems to solve the problem for me too. Could this be because of slow hardware on the client? By slow hardware I mean slow harddrive. I noticed the problem to occure after the initial transfer over the network (from my rsync mirror within my network) when the client disk (slow laptop HD) was working a lot and there was no network activity.
Back to top
View user's profile Send private message
alfonx2
n00b
n00b


Joined: 22 Nov 2005
Posts: 1

PostPosted: Tue Nov 22, 2005 2:31 pm    Post subject: Reply with quote

This error also occurred on my gentoo since a few days. The TIMEOUT setting did not help. But it helped to upgrade to keyworded version rsync-2.6.6-r1 from "stable" version rsync-2.6.0-r6.

just wanted to tell,

alfonx
_________________
internet makes the stupid more stupid and the smart more smart.
Back to top
View user's profile Send private message
humbletech99
Veteran
Veteran


Joined: 26 May 2005
Posts: 1229
Location: London

PostPosted: Tue Dec 13, 2005 3:57 pm    Post subject: Reply with quote

I have an old PII with the same problem, but it seems as though it's not the machine's fault because top shows that rsync is using only between 1-12% cpu and it can't be maxing out the disk. The net connection is a 2Mb business line. What gives?
Back to top
View user's profile Send private message
humbletech99
Veteran
Veteran


Joined: 26 May 2005
Posts: 1229
Location: London

PostPosted: Tue Dec 13, 2005 4:04 pm    Post subject: Reply with quote

well with the help of that RSYNC variable I've gotten past the stupid rsync and back to the updating portage cache where I was before but I think it'll still time out the rate that thing is going! However emerge is only using 35% of my CPU...
Back to top
View user's profile Send private message
humbletech99
Veteran
Veteran


Joined: 26 May 2005
Posts: 1229
Location: London

PostPosted: Tue Dec 13, 2005 4:57 pm    Post subject: Reply with quote

ok ,it finally completed after an absolute age but that RSYNC variable seems to have helped it. thanks.
Back to top
View user's profile Send private message
bens
n00b
n00b


Joined: 03 Mar 2004
Posts: 37
Location: MIT

PostPosted: Thu Dec 15, 2005 6:16 am    Post subject: Same problem Reply with quote

Same problem here. Must be something with portage, or maybe with gcc 3.4.4 and rsync.
Back to top
View user's profile Send private message
humbletech99
Veteran
Veteran


Joined: 26 May 2005
Posts: 1229
Location: London

PostPosted: Thu Dec 15, 2005 9:22 am    Post subject: Reply with quote

it's more likely that portage was designed with faster machines in mind, I've never had this problem with newer machines, just this crappy old 350MHz 128MB Ram which is otherwise dustbin fodder...

Althought the connection may also be a problem, it's probably not supposed to be used on slow connections (although the connection here is quite reasonable 2Mb)
Back to top
View user's profile Send private message
bens
n00b
n00b


Joined: 03 Mar 2004
Posts: 37
Location: MIT

PostPosted: Fri Dec 16, 2005 12:52 am    Post subject: Strange Reply with quote

My problem turned out to be that an rsync process had gotten stuck in the "D" state, and then so had every other rsync process after it, as if they had all piled up. A reboot fixed it.
Back to top
View user's profile Send private message
humbletech99
Veteran
Veteran


Joined: 26 May 2005
Posts: 1229
Location: London

PostPosted: Fri Dec 16, 2005 9:12 am    Post subject: Reply with quote

interesting, I didn't check for that but eventually i managed to get it to work via the addition to make.conf mentioned about. If it happens again, I'll have a look at that, although I think that the process was at the top of the "top" screen all the time...
Back to top
View user's profile Send private message
yfh2
Apprentice
Apprentice


Joined: 20 May 2004
Posts: 242

PostPosted: Tue Jun 27, 2006 8:05 pm    Post subject: Reply with quote

Well, suddently, I can't rsync either.

What happened is :
I Installed a fresh 2006 system on my newly arrived AMD64x2 (SATA HD), and I could not emerge sync.
It would hang the same way.

Then, I tried to emerge sync on my current machine, which I synced last week and ... same problem !

I have not tried the 'RSYNC_TIMEOUT=500' trick, because as far as I know, I expect the other end to work ...
Back to top
View user's profile Send private message
magnesium
Apprentice
Apprentice


Joined: 28 Oct 2003
Posts: 280
Location: Toronto, Canada

PostPosted: Sat Jul 15, 2006 4:52 pm    Post subject: Reply with quote

Increasing your timeout value is good if you have a slow machine or perhaps one that is really bogged down too.

Note: RSYNC_TIMEOUT is now depricated and it's just a matter of time before it's no longer supported. Change your /etc/make.conf to use PORTAGE_RSYNC_EXTRA_OPTS="--timeout=500" if you were previously using RSYNC_TIMEOUT=500.
_________________
Adopt an unanswered post
Back to top
View user's profile Send private message
sarathms
n00b
n00b


Joined: 21 Apr 2005
Posts: 3

PostPosted: Sat Jan 13, 2007 9:11 pm    Post subject: upgrade 'rsync' Reply with quote

in my case the problem disappeared after i upgraded the 'rsync' package to rsync-2.6.9
didn't have to modify the /etc/make.conf file
_________________
emerge gentoo
Back to top
View user's profile Send private message
KejPi
Tux's lil' helper
Tux's lil' helper


Joined: 17 Jan 2004
Posts: 122
Location: Prague, Czech republic

PostPosted: Mon Feb 26, 2007 6:50 pm    Post subject: Reply with quote

Hi there,

I have some problem with rsync on amd64 platform. This is what I am always getting:

Code:

rsync: writefd_unbuffered failed to write 4092 bytes [generator]: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(1122) [generator=2.6.9]
rsync error: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9]
>>> Retrying...


I have tied to set rsync timeout to 500 and even to 2000 and it didn't help.

Any suggestions?

Thanks.
Back to top
View user's profile Send private message
Paulathome
n00b
n00b


Joined: 05 Jan 2006
Posts: 17

PostPosted: Thu Nov 22, 2007 7:30 pm    Post subject: Reply with quote

Hi folks,

I am getting similar message as other in this thread ... rsync timeout with code 30.

I have tried updating make.conf and changed the timeout to 500 but it still fails (just takes longer to fail!). The last time i manged to run a sucessful emerge --sync was about 2 weeks ago but I have only tried once or twice since then. My pretty useless ISP have "upgraded" their satellite link over the last few days and my internet performance has improved a little so I dont think it is network related.. certainly network performace seems better and even when it was real bad in the past, rsync usually managed to work (If slowly)..


Does anyone know of any reason why this may be happening and what I can do to fix?

Thanks alot!

Paul.
Back to top
View user's profile Send private message
phimanhhoan
n00b
n00b


Joined: 01 Dec 2007
Posts: 1
Location: Hanoi, Vietnam

PostPosted: Sat Dec 01, 2007 6:34 pm    Post subject: Reply with quote

Hi KejPi,
KejPi wrote:
Hi there,

I have some problem with rsync on amd64 platform. This is what I am always getting:

Code:

rsync: writefd_unbuffered failed to write 4092 bytes [generator]: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(1122) [generator=2.6.9]
rsync error: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9]
>>> Retrying...


I have tied to set rsync timeout to 500 and even to 2000 and it didn't help.

Any suggestions?

Thanks.


I've got an amd64 too and problem's message like your too.
But when I update rsync from rsync-2.6.9-r2 to rsync-2.6.9-r4, everything had gone! No I can emerge --sync normally.

good luck.
Back to top
View user's profile Send private message
net-0
Tux's lil' helper
Tux's lil' helper


Joined: 04 Dec 2006
Posts: 103
Location: Lodi, California

PostPosted: Sun Jan 06, 2008 9:45 am    Post subject: Reply with quote

I seem to keep getting this when I sync,

Code:
receiving file list ... done
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [generator=2.6.9]rsync error: received SIGUSR1 (code 19) at main.c(1185) [receiver=2.6.9]


Any ideas?

I can sync via the web based sync....

--neto
_________________
We built this city on swedish melodic death metal.
Back to top
View user's profile Send private message
greenrd
n00b
n00b


Joined: 24 Oct 2007
Posts: 4
Location: Dublin, Ireland

PostPosted: Wed Feb 27, 2008 11:02 pm    Post subject: Solution Reply with quote

I think in my case it was due to an upstream router dropping connections quite quickly. Here is my solution, which worked swimmingly:

Add this line to /etc/make.conf:

PORTAGE_RSYNC_EXTRA_OPTS="--delete-after --timeout=500"
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum