When I try to run emerge rsync it goes through the retries and timesout each time. If I do a rescue portage to version 2.0.47-r10, I can then do a sync, but have to use a sandbox option to upgrade portage. When portage is upgraded it doesn't matter if it is r15 or r18 the problem then reoccurs. See below: emerge sync >>> starting rsync with rsync://rsync.gentoo.org/gentoo-portage... This is rsync2.us.gentoo.org, located in Florida, USA. receiving file list ... io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) >>> Starting retry 1 of 3 This is rsync2.us.gentoo.org, located in Florida, USA. receiving file list ... io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) >> Starting retry 2 of 3 receiving file list ... io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) >>> Starting retry 3 of 3 CEDE Gentoo Mirror receiving file list ... io timeout after 180 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) !!! 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. Reproducible: Always Steps to Reproduce: 1.rescue to portage-2.0.47-r10 repair replaced files can emerge sync 2.upgrade to portage-2.0.47-r15 or portage-2.0.47-r18 cannot emerge sync timesout 3. Expected Results: Would like to be able to rsync without having to rescue portage and repair the files this replaces.
Sounds like a portage bug rather than a mirror bug. Re-assigning to the portage team.
Hello Virginia, Do you use proxy or something? And can you show us 'emerge info' and `grep SYNC /etc/make.conf`
Here is the information you requested: No I do not use a proxy. I'm using Shorewall as a firewall. It causes no problems until portage is upgraded as I mentioned in the bug report. Here is my 'emerge info' Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.22) ================================================================= System uname: 2.4.22 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://ibiblio.org/pub/Linux/distributions/gentoo/ http://www.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://mirror.iawnet.sandia.gov/pub/gentoo/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/ http://gentoo.seren.com/gentoo http://gentoo.noved.org/ ftp://gentoo.noved.org/ http://gentoo.chem.wisc.edu/gentoo/ http://cudlug.cudenver.edu/gentoo/ ftp://cudlug.cudenver.edu/pub/mirrors/distributions/gentoo/ http://gentoo.ccccom.com ftp://gentoo.ccccom.com http://oss.redundant.com/pub/gentoo ftp://oss.redundant.com/pub/gentoo http://mirrors.tds.net/gentoo ftp://mirrors.tds.net/gentoo http://gentoo.netnitco.net ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ http://mirror.tucdemonic.org/gentoo/ http://mirror.clarkson.edu/pub/distributions/gentoo/ http://128.213.5.34/gentoo/ http://lug.mtu.edu/gentoo/ ftp://lug.mtu.edu/gentoo/source" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb cdr crypt cups directfb encode esd foomaticdb gdbm gif gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline sdl slang spell ssl svga tcltk tcpd truetype usb x86 xml2 xmms xv zlib" Here is the `grep SYNC /etc/make.conf`: grep SYNC /etc/make.conf #SYNC="rsync://rsync16.us.gentoo.org/gentoo-portage" # RSYNC_RETRIES sets the number of times portage will attempt to retrieve #RSYNC_RETRIES="10"
Thanks you for the infomation. But I don't understand. hmm. I just compared 2.0.49-r15 with 2.0.47-r10 about "emerge sync". They are same about "emerge sync". (but thare are a little different in -18). It might be just timeout. Can you set "RSYNC_TIMEOUT=500" in /etc/rsync.conf and retry it?
That may be where the problem is. I no longer have an /etc/rsync.conf file. I don't have a clue as to what is supposed to be in this file. I'm fairly new to Gentoo. I tried creating this file but it only contains the RSYNC_TIMEOUT=500 and I still have the problem.
Sorry, "/etc/rsync.conf" is my typo. "/etc/make.conf" is correct.
OK, I put the RSYNC_TIMEOUT=500 in /etc/make.conf. When running 'emerge sync' it is still just sitting there at the point where it says receiving files. It is doing nothing.
if you disable the firewall and attempt to rsync does it work fine ?
No it still does the same thing.
You are certain that you have the firewall disabled? If setting the timeout to 500 doesn't fix it, I don't quite see what the issue is. You can set it higher and try again. Are you on a modem? What kind of connection?
Yes, I am certain the firewall was disabled. I issued the command "/etc/init.d/shorewall stop" Then I tried the command "emerge sync" It still times out same as with shorewall running. This morning I even tried opening port 873 with shorewall which is the rsync port. I still get the timeouts when using "emerge sync" I am using a modem. Everything worked just fine with "emerge sync" up until just before I filed this bug report. I have tried the use flag of -ipv6 and everything else that I have been able to find on the portage forum. I have re-emerged portage, rsync, and wget several times both with ipv6 and without ipv6. Nothing I've tried has solved the problem. I even tried re-emerging my system files. That didn't work either. I'm beginning to wonder if I may be missing something in the rsyncd.conf file.
I will tell you again, increasing the timeout time does not do any good. During the time it says it is receiving the file list, absolutely nothing is happening. Before this problem started occuring, it was actually receiving the file list. It showed the number of files it had received and the modem indicator showed it was doing something. Now none of this is occuring. It is just sitting there, timesout and then moves on to try another mirror where the same thing happens all over again.
Are you using pam-0.77 ? I had a similar problem and it went away after downgrading to pam-0.75. Strange thing is, I upgraded back to pam-0.77 and it works. It looks like the pam-0.77 ebuild has changed since I originally emerged it, but nothing that looks relevant to me.
Portage does nothing special with rsync other than settings the timeout to 180 seconds by default. If this is still an issue, try setting the timeout to something around 2400 seconds. The file list is over 1.5M and at 5 minute megs, you're looking at 7-8 minutes... PLUS the delay for IO on either side. As far as portage is concerned, nothing can be done.
Note: Try 'emerge-webrsync' as an alternative to 'emerge --sync'. The port may be blocked somewhere between you and the servers.
