| 1 |
Date: Mon, 17 Sep 2007 02:15:59 -0400 |
| 2 |
From: Walter Dnes <waltdnes@××××××××.org> |
| 3 |
To: Gentoo Users List <gentoo-user@g.o> |
| 4 |
Subject: emerge --sync stopped working |
| 5 |
Message-ID: <20070917061559.GA23905@××××××××.org> |
| 6 |
|
| 7 |
I went almost a month without updating. My old machine (1999 Dell |
| 8 |
450 mhz PIII) finally died. I had kept a newer AMD 3000+ updated as my |
| 9 |
"hot backup". The switchover went smoothly. I had just moved, and was |
| 10 |
busy setting up my new condo, and fighting the install on a new Dell. I |
| 11 |
finally got the new Dell set up, so I dared to update the AMD. |
| 12 |
|
| 13 |
It was a major struggle. "emerge --sync" stopped working. I manually |
| 14 |
selected a different rsync server, and got the same error messages. I |
| 15 |
gave up and used webrsync. |
| 16 |
|
| 17 |
This weekend was spent fighting several update issues. I've finally |
| 18 |
gotten X working again and revdep-rebuild doesn't flag any problems, so |
| 19 |
back to the "emerge --sync" issue. I don't see anything on Bugzilla |
| 20 |
that looks like my problem. Before I file a bug, are there any obvious |
| 21 |
things to check first? |
| 22 |
|
| 23 |
At the bottom is a listing of the attempt. In addition to the attempt |
| 24 |
below, I changed the server in /etc/make.conf manually a couple of times |
| 25 |
and the the same errors with other servers. I also tried downgrading |
| 26 |
from 2.6.3-r3 to -r2 and -r1, and got the same errors. Any ideas? |
| 27 |
|
| 28 |
[m3000][root][~] emerge --sync |
| 29 |
>>> Starting rsync with rsync://134.153.48.2/gentoo-portage... |
| 30 |
>>> Checking server timestamp ... |
| 31 |
timed out |
| 32 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9] |
| 33 |
>>> Retrying... |
| 34 |
|
| 35 |
|
| 36 |
>>> Starting retry 1 of 3 with rsync://132.207.4.160/gentoo-portage |
| 37 |
>>> Checking server timestamp ... |
| 38 |
rsync: read error: Connection reset by peer (104) |
| 39 |
rsync error: error in rsync protocol data stream (code 12) at io.c(609) [receiver=2.6.9] |
| 40 |
>>> Retrying... |
| 41 |
|
| 42 |
|
| 43 |
>>> Starting retry 2 of 3 with rsync://142.77.49.220/gentoo-portage |
| 44 |
>>> Checking server timestamp ... |
| 45 |
timed out |
| 46 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9] |
| 47 |
>>> Retrying... |
| 48 |
|
| 49 |
|
| 50 |
>>> Starting retry 3 of 3 with rsync://216.194.64.133/gentoo-portage |
| 51 |
>>> Checking server timestamp ... |
| 52 |
timed out |
| 53 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9] |
| 54 |
|
| 55 |
!!! Rsync has not successfully finished. It is recommended that you keep |
| 56 |
!!! trying or that you use the 'emerge-webrsync' option if you are unable |
| 57 |
!!! to use rsync due to firewall or other restrictions. This should be a |
| 58 |
!!! temporary problem unless complications exist with your network |
| 59 |
!!! (and possibly your system's filesystem) configuration. |
| 60 |
|
| 61 |
-- |
| 62 |
Walter Dnes <waltdnes@××××××××.org> In linux /sbin/init is Job #1 |
| 63 |
Q. Mr. Ghandi, what do you think of Microsoft security? |
| 64 |
A. I think it would be a good idea. |
| 65 |
-- |
| 66 |
gentoo-user@g.o mailing list |
Archives