Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 350273 - emerge --sync fails
Summary: emerge --sync fails
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-01 09:57 UTC by John L. Poole
Modified: 2011-01-01 10:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John L. Poole 2011-01-01 09:57:47 UTC
I have a Gentoo rsync server runnning on 192.168.168.15.  I have several Gentoo machines that sync to it without any problem; I've had this server running for about 2 years.  When I try to "emerge --sync" from my laptop ("themis" an Intel i5 dual core), I get the error message below which is not descriptive.

Yet, at the same time I have another server (at 192.168.168.16) successfully syncing to #15.  Therefore, it appears something is awry with my laptop's system that causes the above error which is not indicative of the problem.

Reproducible: Always

Steps to Reproduce:
1. emerge --sync

Actual Results:  
When I try to "emerge --sync" from my laptop, I get:
themis jlpoole # emerge --sync
>>> Starting rsync with rsync://192.168.168.15/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...
!!! Exhausted addresses for 192.168.168.15
themis jlpoole #

Expected Results:  
successful sync of portage

my /etc/make.conf has:

#SYNC=rsync8.us.gentoo.org
SYNC="rsync://192.168.168.15/gentoo-portage"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu"
...

#
# for cross compiling
# 
PORTDIR_OVERLAY=/usr/local/portage
Comment 1 John L. Poole 2011-01-01 10:07:36 UTC
my error.  I was on a different wireless network that the server 192.168.168.15 was not on.

This is not a bug.