public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthew Closson <matt@scrapshells.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] emerge --sync timeouts
Date: Mon, 2 Jan 2006 17:09:57 -0500 (EST)	[thread overview]
Message-ID: <Pine.BSO.4.62.0601021703440.15874@carnivore.scrapshells.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed, Size: 2566 bytes --]

Hello,

When I have not sync'd in over a month or so and when I ran:

emerge --sync
It basically shows the motd of the remote rsync server and then times out.
I have let it run for a bit and try multiple servers and it just keeps 
timing out after the motd regardless of which server it goes to... here is 
some output:


--------------------------------------------------------------------------
Script started on Mon Jan  2 16:46:45 2006
sh-3.00# emerge --sync
^[]2;Started emerge on: Jan 02, 2006 16:46:54\a^[]2; *** emerge  sync\a^[]2; === sync\a^[]2;>>> starting rsync with rsync://64.127.121.98/gentoo-portage\a>>> starting rsync with rsync://64.127.121.98/gentoo-portage...
>>> checking server timestamp ...
Welcome to owl.gentoo.org

Server Address : 64.127.121.98
Contact Name   : mirror-admin@gentoo.org
Hardware       : 4 x Intel(R) Xeon(TM) CPU 2.40GHz, 1024MB RAM


Please note: common gentoo-netiquette says you should not sync more
than once a day.  Users who abuse the rsync.gentoo.org rotation
may be added to a temporary ban list.


MOTD brought to you by motd-o-matic, version 0.3

io timeout after 180 seconds - exiting
rsync error: timeout in data send/receive (code 30) at io.c(109)
>>> retry ...
^[]2;>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage\a

>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
>>> checking server timestamp ...
Welcome to raven.gentoo.org

Server Address : 134.68.220.73
Contact Name   : mirror-admin@gentoo.org
Hardware       : 2 x Intel(R) Xeon(TM) CPU 1700MHz, 2176MB RAM


Please note: common gentoo-netiquette says you should not sync more
than once a day.  Users who abuse the rsync.gentoo.org rotation
may be added to a temporary ban list.


MOTD brought to you by motd-o-matic, version 0.3

--------------------------------------------------------------------------

and thats it.  I reinstalled a recent portage snapshot and also made sure 
I don't have any config file updates pending with etc-update and a manual 
search in etc.  The rest of portage/emerge continues to work fine.  I can 
continue to emerge/install packages without problems, just not --sync. 
Any ideas are appreciated.  Thanks,

 			-Matt-

DFI Lanparty UT Ultra-D SLI-mod 6.18-2 
A64 3000 Venice 300x9 1.50V 
Kingwin AWC-1 water cooled 30C/42C 
2x512 TwinMOS PC3200 BH-5 @ 245 3.4V 
Rosewill X800XL 459/1100 37C/50C volt modded 
Some cheap ass hard drives 
Some non-color matching optical drives 
Fortron 500w Blue Storm 
Gentoo Linux x86 OS 
Fluxbox Window manager

-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2006-01-02 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02 22:09 Matthew Closson [this message]
2006-01-02 22:59 ` [gentoo-user] emerge --sync timeouts Zac Medico
2006-01-03  1:06 ` Bastiaan Visser
2006-01-02 22:54   ` [gentoo-user] Re: [solved] " Matthew Closson
2006-01-03  0:43     ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSO.4.62.0601021703440.15874@carnivore.scrapshells.com \
    --to=matt@scrapshells.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox