[gentoo-user] problems with rsync (emerge --sync)

[gentoo-user] problems with rsync (emerge --sync)

[Rod]

     Hi, has anyone had this problem with trying to update the database 
for portage?

     It was doing this a while ago, then it stopped (I don't know why) 
now its doing it again..

# emerge --sync
 >>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
 >>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at 
rsync.c(543) [Receiver=3.0.7]
 >>> Retrying...


 >>> Starting retry 1 of 3 with rsync://134.68.240.59/gentoo-portage
 >>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at 
rsync.c(543) [Receiver=3.0.7]
 >>> Retrying...


 >>> Starting retry 2 of 3 with rsync://88.198.83.250/gentoo-portage
 >>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at 
rsync.c(543) [Receiver=3.0.7]
 >>> Retrying...


 >>> Starting retry 3 of 3 with rsync://88.198.83.249/gentoo-portage
 >>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at 
rsync.c(543) [Receiver=3.0.7]
 >>> Exceeded PORTAGE_RSYNC_RETRIES: 3

Re: [gentoo-user] problems with rsync (emerge --sync)

[Peter Ruskin]

On Thursday 03 June 2010 13:43:55 Rod wrote:
>      Hi, has anyone had this problem with trying to update the
> database for portage?
>
>      It was doing this a while ago, then it stopped (I don't know
> why) now its doing it again..
>
> # emerge --sync
>  >>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
>  >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
> rsync.c(543) [Receiver=3.0.7]
>  >>> Retrying...

It happend a lot here in the UK too.  The mirrors seem not up to 
snuff.

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.2_rc67			kernel-2.6.34-gentoo
AMD Phenom(tm) 9950 Quad-Core Processor		gcc(Gentoo: 4.4.3-r2)
KDE: 3.5.10					Qt: 3.3.8b
========================================================================

[gentoo-user] Re: problems with rsync (emerge --sync)

[walt]

On 06/03/2010 05:43 AM, Rod wrote:
>   Hi, has anyone had this problem with trying to update the database for portage?
>
> It was doing this a while ago, then it stopped (I don't know why) now its doing it again..
>
> # emerge --sync
>  >>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
>  >>> Checking server timestamp ...
> timed out

If you don't specify a list of mirrors you want, portage will rotate randomly through
its list.  You'll probably get better results if you pick a handful of servers that
are close to you and not overloaded.  Emerge mirrorselect and see if you can get
better servers.

Re: [gentoo-user] Re: problems with rsync (emerge --sync)

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1143 bytes --]

On Thursday 03 June 2010 19:55:29 walt wrote:
> On 06/03/2010 05:43 AM, Rod wrote:
> >   Hi, has anyone had this problem with trying to update the database for
> > portage?
> >
> > It was doing this a while ago, then it stopped (I don't know why) now its
> > doing it again..
> >
> > # emerge --sync
> >
> >  >>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
> >  >>> Checking server timestamp ...
> >
> > timed out
> 
> If you don't specify a list of mirrors you want, portage will rotate
>  randomly through its list.  You'll probably get better results if you pick
>  a handful of servers that are close to you and not overloaded.  Emerge
>  mirrorselect and see if you can get better servers.

I'm also getting this.  Initially I thought that DNS could not resolve for 
some ISP related reason, but it is more involved than that.  It seems like a 
$SYNC not a $GENTOO_MIRRORS problem.

I changed the rsync.europe.gentoo.org to rsync.de.gentoo.org and rsync worked.  
So, could it be that something is wrong with the way the rsync rsync.europe 
mirrors are meant to be rotated?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: problems with rsync (emerge --sync)

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1310 bytes --]

On Friday 04 June 2010 08:37:00 Mick wrote:
> On Thursday 03 June 2010 19:55:29 walt wrote:
> > On 06/03/2010 05:43 AM, Rod wrote:
> > >   Hi, has anyone had this problem with trying to update the database
> > > for portage?
> > >
> > > It was doing this a while ago, then it stopped (I don't know why) now
> > > its doing it again..
> > >
> > > # emerge --sync
> > >
> > >  >>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
> > >  >>> Checking server timestamp ...
> > >
> > > timed out
> >
> > If you don't specify a list of mirrors you want, portage will rotate
> >  randomly through its list.  You'll probably get better results if you
> > pick a handful of servers that are close to you and not overloaded. 
> > Emerge mirrorselect and see if you can get better servers.
> 
> I'm also getting this.  Initially I thought that DNS could not resolve for
> some ISP related reason, but it is more involved than that.  It seems like
>  a $SYNC not a $GENTOO_MIRRORS problem.
> 
> I changed the rsync.europe.gentoo.org to rsync.de.gentoo.org and rsync
>  worked. So, could it be that something is wrong with the way the rsync
>  rsync.europe mirrors are meant to be rotated?

Any progress with this guys?  Should we be filling in a bug report?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]