From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ilr9u-0004UH-K9 for garchives@archives.gentoo.org; Sat, 27 Oct 2007 19:17:23 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.1/8.14.0) with SMTP id l9RJCxTu007670; Sat, 27 Oct 2007 19:12:59 GMT Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by robin.gentoo.org (8.14.1/8.14.0) with ESMTP id l9RJCw5w007649 for ; Sat, 27 Oct 2007 19:12:58 GMT Received: by fk-out-0910.google.com with SMTP id 19so2124482fkr for ; Sat, 27 Oct 2007 12:12:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=qEMrrLfBsbK42fVoZtlXMHQK4kjJrWjevPBJIR89U5w=; b=Dnz0EDNTDIIv5oAKsAchnuEUE5l317bSImCwc3sPHjKLrS7v1kNa+1RHFcayVyJIj0ID78ktHKIkykj38SZXCZVQwbJCJRD3RMvnd7L83BVXxajk0/z8Xc+iximK6qwydRUToK/c30B8WGZ49cJoW2K/bdFgQo9JPqnHetbd+5k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=avxQwLxWHiv/OHoRSLBNk7aWXx2n0Iom45M7RwkJk+BzzLZqKU1Ru80mw76IJhSKjDDUFvpPt2ut6M1BEWlD09R+nIUOHW1hq4Wl2kXivWYksDViqDbGpuAByqKznvmtTuuGlt3Izq/TevebFNPXEZdO5YD0KjnFczO/QPc7GUs= Received: by 10.82.175.17 with SMTP id x17mr8377148bue.1193512377989; Sat, 27 Oct 2007 12:12:57 -0700 (PDT) Received: by 10.82.135.4 with HTTP; Sat, 27 Oct 2007 12:12:57 -0700 (PDT) Message-ID: Date: Sat, 27 Oct 2007 21:12:57 +0200 From: Beso To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] emerge --sync failed In-Reply-To: <200710271559.19682.gentoo@appjaws.plus.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14147_30907690.1193512377838" References: <200710271443.03861.gentoo@appjaws.plus.com> <20071027094738.3c73939f@Midori.localhost> <200710271559.19682.gentoo@appjaws.plus.com> X-Archives-Salt: 27ac1633-5608-464f-9abc-5a0a3d3c769b X-Archives-Hash: 1a7250d8b940923dffeb2dd2d11501cd ------=_Part_14147_30907690.1193512377838 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline probably the rsync has changed ip. try one of this servers: sync = rsync://rsync.gentoo.org/gentoo-portage #sync = rsync://rsync3.it.gentoo.org/gentoo-sources #sync = http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/ #sync = http://mirror.ing.unibo.it/gentoo/ the first is the official one, the others should be mirrors. a full list of rsync mirrors can be found somewhere on the gentoo site. just search for it. the problem with your method is that you don't pass through a dns server asking directly for an ip address and this could not work anymore when the site you're trying has changed ip. you'd have to get again the ip. if you want to use the ip address try searching the name with a ping or traceroute or in some dns site like in the opendns cache site. 2007/10/27, Paul Stear : > > On Saturday 27 October 2007, Kenneth Prugh wrote: > > On Sat, 27 Oct 2007 14:43:03 +0100 > > > > Paul Stear wrote: > > > Hi all, > > > I'm sorry if this has been covered but I have had trouble with my > > > mail. I use the command eix-sync && emerge -auvtDN world && prelink > > > -aqR to update my system. However, since Friday I am getting the > > > following output:- > > > * Removing old portage-cache in /var/cache/edb/dep ... > > > {ok ] > > > * Running emerge --sync ... > > > * Problems running time emerge --sync > > > [ !! ] > > > * emerge --sync failed > > > > > > Has anybody any ideas as to what is causing this and how to solve it? > > > Thanks > > > Paul > > > > Not sure, but does `emerge --sync` actually work? That would probably > > give a more detailed error than eix does. > > Hi, this is the error for emerge --sync:- > >>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage > >>> Checking server timestamp ... > timed out > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) > [receiver=2.6.9] > >>> Retrying... > > > >>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage > >>> Checking server timestamp ... > timed out > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) > [receiver=2.6.9] > > So it appears a time out problem. What should I do now? > Thanks > Paul > -- > This message has been sent using kmail with gentoo linux > -- > gentoo-amd64@gentoo.org mailing list > > -- dott. ing. beso ------=_Part_14147_30907690.1193512377838 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline probably the rsync has changed ip. try one of this servers:
sync = rsync://rsync.gentoo.org/gentoo-portage
#sync = rsync://rsync3.it.gentoo.org/gentoo-sources
#sync = http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/
#sync = http://mirror.ing.unibo.it/gentoo/
the first is the official one, the others should be mirrors. a full list of rsync mirrors can be found somewhere on the gentoo site. just search for it. the problem with your method is that you don't pass through a dns server asking directly for an ip address and this could not work anymore when the site you're trying has changed ip. you'd have to get again the ip. if you want to use the ip address try searching the name with a ping or traceroute or in some dns site like in the opendns cache site.

2007/10/27, Paul Stear <gentoo@appjaws.plus.com>:
On Saturday 27 October 2007, Kenneth Prugh wrote:
> On Sat, 27 Oct 2007 14:43:03 +0100
>
> Paul Stear <gentoo@appjaws.plus.com> wrote:
> > Hi all,
> > I'm sorry if this has been covered but I have had trouble with my
> > mail. I use the command eix-sync && emerge -auvtDN world && prelink
> > -aqR to update my system. However, since Friday I am getting the
> > following output:-
> > * Removing old portage-cache in /var/cache/edb/dep ...
> > {ok ]
> >  * Running emerge --sync ...
> >  * Problems running time emerge --sync
> > [ !! ]
> >  * emerge --sync failed
> >
> > Has anybody any ideas as to what is causing this and how to solve it?
> > Thanks
> > Paul
>
> Not sure, but does `emerge --sync` actually work? That would probably
> give a more detailed error than eix does.

Hi, this is the error for emerge --sync:-
>>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
[receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
[receiver=2.6.9]

So it appears a time out problem. What should I do now?
Thanks
Paul
--
This message has been sent using kmail with gentoo linux
--
gentoo-amd64@gentoo.org mailing list




--
dott. ing. beso ------=_Part_14147_30907690.1193512377838-- -- gentoo-amd64@gentoo.org mailing list