Bug 169720

Summary:	rsync://134.68.220.97 connection timeout
Product:	Mirrors	Reporter:	Jakub Moc (RETIRED) <jakub>
Component:	Server Problem	Assignee:	Mirror Admins <mirror-admin>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	burn
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Jakub Moc (RETIRED) gentoo-dev

2007-03-07 09:41:46 UTC

About third time I did hit this in past few days, anyone else can confirm?

>>> Starting rsync with rsync://134.68.220.97/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...

Comment 1 Robert Baxter 2007-03-07 10:26:08 UTC

Works for me.

[03:25:02]<root@echo:~> SYNC="rsync://134.68.220.97/gentoo-portage" emerge --sync
>>> Starting rsync with rsync://134.68.220.97/gentoo-portage...
>>> Checking server timestamp ...
Welcome to hawk.gentoo.org

Server Address : 134.68.220.97
Contact Name   : mirror-admin@gentoo.org
Hardware       : 1 x Intel(R) Pentium(R) 4 CPU 2.40GHz, 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

Comment 2 Raúl Porcel (RETIRED) gentoo-dev

2007-03-07 10:46:04 UTC

wfm

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2007-03-07 10:48:54 UTC

Hmmm 'kay, thanks for testing. I'll retry later.