[gentoo-user] emerge --sync stopped working

[gentoo-user] emerge --sync stopped working

[Walter Dnes]

Date: Mon, 17 Sep 2007 02:15:59 -0400
From: Walter Dnes <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@gentoo.org>
Subject: emerge --sync stopped working
Message-ID: <20070917061559.GA23905@waltdnes.org>

  I went almost a month without updating.  My old machine (1999 Dell
450 mhz PIII) finally died.  I had kept a newer AMD 3000+ updated as my
"hot backup".  The switchover went smoothly.  I had just moved, and was
busy setting up my new condo, and fighting the install on a new Dell.  I
finally got the new Dell set up, so I dared to update the AMD.

  It was a major struggle. "emerge --sync" stopped working.  I manually
selected a different rsync server, and got the same error messages.  I
gave up and used webrsync.

  This weekend was spent fighting several update issues.  I've finally
gotten X working again and revdep-rebuild doesn't flag any problems, so
back to the "emerge --sync" issue.  I don't see anything on Bugzilla
that looks like my problem.  Before I file a bug, are there any obvious
things to check first?

  At the bottom is a listing of the attempt.  In addition to the attempt
below, I changed the server in /etc/make.conf manually a couple of times
and the the same errors with other servers.  I also tried downgrading
from 2.6.3-r3 to -r2 and -r1, and got the same errors.  Any ideas?

[m3000][root][~] emerge --sync
>>> Starting rsync with rsync://134.153.48.2/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 1 of 3 with rsync://132.207.4.160/gentoo-portage
>>> Checking server timestamp ...
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(609) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 2 of 3 with rsync://142.77.49.220/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://216.194.64.133/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]

!!! 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.

-- 
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
Q. Mr. Ghandi, what do you think of Microsoft security?
A. I think it would be a good idea.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync stopped working

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

On Mon, 17 Sep 2007 07:32:18 -0400, Walter Dnes wrote:

> I had just moved, and was busy setting up my new condo,

[snip]

>   It was a major struggle. "emerge --sync" stopped working.  I manually
> selected a different rsync server, and got the same error messages.  I
> gave up and used webrsync.

Did you change ISPs when moving? Does your new ISP block rsync traffic?


-- 
Neil Bothwick

deja noo - reminds you of the last time you visited Scotland

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] emerge --sync stopped working

[Naga]

On Monday 17 September 2007 13:32:18 Walter Dnes wrote:
> and the the same errors with other servers.  I also tried downgrading
> from 2.6.3-r3 to -r2 and -r1, and got the same errors.  Any ideas?
           ^^^^
>
> [m3000][root][~] emerge --sync
>
> >>> Starting rsync with rsync://134.153.48.2/gentoo-portage...
> >>> Checking server timestamp ...
>
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
                    ^^^^
Tried upgrading to a version in portage (2.6.9-r1 2.6.9-r2 2.6.9-r3)?
Could be a version incompability issue.

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync stopped working

[Walter Dnes]

On Mon, Sep 17, 2007 at 03:00:40PM +0200, Naga wrote
> On Monday 17 September 2007 13:32:18 Walter Dnes wrote:
> > and the the same errors with other servers.  I also tried
> > downgrading
> > from 2.6.3-r3 to -r2 and -r1, and got the same errors.  Any ideas?
>            ^^^^

> Tried upgrading to a version in portage (2.6.9-r1 2.6.9-r2 2.6.9-r3)?
> Could be a version incompability issue.

  Sorry about that typo.  That was supposed to read 2.6.9, and I tried
-r1, -r2, and -r3.

-- 
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
Q. Mr. Ghandi, what do you think of Microsoft security?
A. I think it would be a good idea.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync stopped working

[Walter Dnes]

On Mon, Sep 17, 2007 at 01:35:24PM +0100, Neil Bothwick wrote

> Did you change ISPs when moving? Does your new ISP block rsync traffic?

  Bingo.  Same ISP.  Things worked OK after the move for about a month
after the move.  Since about Sept 8th, however, I haven't been able to
send out email via my broadband ISP.  I've had to fall back to my dialup
ISP, which I deliberately use a different provider for.  Their name, and
website, is 295.ca so guess how much they charge per month.

  Anyhow, I just ran a successful emerge --sync via dialup.  I have some
complaining to do.

-- 
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
Q. Mr. Ghandi, what do you think of Microsoft security?
A. I think it would be a good idea.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync stopped working

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Walter Dnes wrote:
> On Mon, Sep 17, 2007 at 01:35:24PM +0100, Neil Bothwick wrote
>
>   
>> Did you change ISPs when moving? Does your new ISP block rsync traffic?
>>     
>
>   Bingo.  Same ISP.  Things worked OK after the move for about a month
> after the move.  Since about Sept 8th, however, I haven't been able to
> send out email via my broadband ISP.  I've had to fall back to my dialup
> ISP, which I deliberately use a different provider for.  Their name, and
> website, is 295.ca so guess how much they charge per month.
>
>   Anyhow, I just ran a successful emerge --sync via dialup.  I have some
> complaining to do.
>
>   

This may not be the problem in your case but when I ran into that
problem on a second machine, my mobo was bad.  I suspect it had
something to do with the PCI bus on mine.  I also found some bad ram on
there too which makes me think maybe a surge hit it or something.

In my case, I tried several different ethernet cards with no help.

Just a thought.

Dale

:-)  :-)  :-)

[-- Attachment #2: Type: text/html, Size: 1459 bytes --]