Is anyone experiencing this problem at the moment? Wondering what is
wrong on my side.
Thanks,
--
Valmor
-> emerge --sync
>>> Starting rsync with rsync://134.68.240.40/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 1 of 3 with rsync://209.177.148.226/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://140.211.166.189/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 3 of 3 with rsync://134.68.240.58/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
>>> Exceeded PORTAGE_RSYNC_RETRIES: 3
07-24-2010, 03:43 AM
Alejandro Pino Oreamuno
timed out rsync error:
same problem here with 134.68.240.59 , 88.198.83.249 , 88.198.83.250 , 140.211.166.189
Alejandro
07-26-2010, 04:14 PM
Albert Hopkins
timed out rsync error:
On Mon, 2010-07-26 at 11:24 -0500, Valmor de Almeida wrote:
> I am still running into the same problem since a couple of days ago. I
> tried both
>
> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
> SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
>
> Is anyone having issues with syncing the portage tree?
I had no problems syncing a few hours ago (I'm just using whatever the
default is).
-a
07-26-2010, 04:19 PM
Mick
timed out rsync error:
On 26 July 2010 17:24, Valmor de Almeida <val.gentoo@gmail.com> wrote:
>
> I am still running into the same problem since a couple of days ago. I
> tried both
>
> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
> SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
>
> Is anyone having issues with syncing the portage tree?
> -> emerge --sync
>>>> Starting rsync 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(544) [receiver=3.0.6]
>>>> Retrying...
[snip ...]
> Alejandro Pino Oreamuno wrote:
>> same problem here with 134.68.240.59 , 88.198.83.249 , 88.198.83.250 ,
>> 140.211.166.189
For a couple of weeks I was having problems with
rsync://rsync.europe.gentoo.org/gentoo-portage and changed it to
rsync://rsync.uk.gentoo.org/gentoo-portage - you may want to change it
to the mirror which is nearest to you (and works). Either try
mirrorselect -i -r -o >> /mnt/gentoo/etc/make.conf to automatically
find a suitable rsync server, have a look here for your nearest rsync
server and set it up manually:
Is anyone having issues with syncing the portage tree?
Thanks,
--
Valmor
-> emerge --sync
>>> Starting rsync 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(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 1 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(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 2 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(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 3 of 3 with rsync://134.68.240.58/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
>>> Exceeded PORTAGE_RSYNC_RETRIES: 3
Alejandro Pino Oreamuno wrote:
> same problem here with 134.68.240.59 , 88.198.83.249 , 88.198.83.250 ,
> 140.211.166.189
>
>
> Alejandro
07-26-2010, 05:38 PM
Valmor de Almeida
timed out rsync error:
Albert Hopkins wrote:
> On Mon, 2010-07-26 at 11:24 -0500, Valmor de Almeida wrote:
>> I am still running into the same problem since a couple of days ago. I
>> tried both
>>
>> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
>> SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
>>
>> Is anyone having issues with syncing the portage tree?
>
> I had no problems syncing a few hours ago (I'm just using whatever the
> default is).
>
> -a
>
>
>
Could you post your SYNC value from your /etc/make.conf file?
Thanks,
--
Valmor
07-26-2010, 05:48 PM
Albert Hopkins
timed out rsync error:
On Mon, 2010-07-26 at 12:38 -0500, Valmor de Almeida wrote:
> > I had no problems syncing a few hours ago (I'm just using whatever
> the
> > default is).
> >
> > -a
> >
> >
> >
> Could you post your SYNC value from your /etc/make.conf file?
>
I don't have a SYNC value in my make.conf. That's what I meant by
"default".
07-26-2010, 05:48 PM
Valmor de Almeida
timed out rsync error:
Mick wrote:
> On 26 July 2010 17:24, Valmor de Almeida <val.gentoo@gmail.com> wrote:
>> I am still running into the same problem since a couple of days ago. I
>> tried both
>>
>> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
>> SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
>>
>> Is anyone having issues with syncing the portage tree?
>
>> -> emerge --sync
>>>>> Starting rsync 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(544) [receiver=3.0.6]
>>>>> Retrying...
> [snip ...]
>
>> Alejandro Pino Oreamuno wrote:
>>> same problem here with 134.68.240.59 , 88.198.83.249 , 88.198.83.250 ,
>>> 140.211.166.189
>
> For a couple of weeks I was having problems with
> rsync://rsync.europe.gentoo.org/gentoo-portage and changed it to
> rsync://rsync.uk.gentoo.org/gentoo-portage - you may want to change it
> to the mirror which is nearest to you (and works). Either try
> mirrorselect -i -r -o >> /mnt/gentoo/etc/make.conf to automatically
> find a suitable rsync server, have a look here for your nearest rsync
> server and set it up manually:
>
> http://www.gentoo.org/main/en/mirrors-rsync.xml
I tried many of those rsync servers in the gentoo web site. No luck.
Maybe my system is broken. I even tried the uk rsync. Don't know where
to go from here...
Thanks,
--
Valmor
07-26-2010, 05:54 PM
Albert Hopkins
timed out rsync error:
On Mon, 2010-07-26 at 12:38 -0500, Valmor de Almeida wrote:
>
> Could you post your SYNC value from your /etc/make.conf file?
Is anyone having issues with syncing the portage tree?
-> emerge --sync
Starting rsync 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(544) [receiver=3.0.6]
Retrying...
[snip ...]
Alejandro Pino Oreamuno wrote:
same problem here with 134.68.240.59 , 88.198.83.249 , 88.198.83.250 ,
140.211.166.189
For a couple of weeks I was having problems with
rsync://rsync.europe.gentoo.org/gentoo-portage and changed it to
rsync://rsync.uk.gentoo.org/gentoo-portage - you may want to change it
to the mirror which is nearest to you (and works). Either try
mirrorselect -i -r -o>> /mnt/gentoo/etc/make.conf to automatically
find a suitable rsync server, have a look here for your nearest rsync
server and set it up manually:
http://www.gentoo.org/main/en/mirrors-rsync.xml
I tried many of those rsync servers in the gentoo web site. No luck.
Maybe my system is broken. I even tried the uk rsync. Don't know where
to go from here...
Thanks,
--
Valmor
I just synced to this server. It worked fine. You may want to try it.
If it doesn't work, then you know something is wrong on your end, if it
does, then there is something weird going on. From my make.conf: