Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 392603 - masterportage.gentoo.org has problems
Summary: masterportage.gentoo.org has problems
Status: RESOLVED FIXED
Alias: None
Product: Mirrors
Classification: Unclassified
Component: Server Problem (show other bugs)
Hardware: All Linux
: Normal critical
Assignee: Mirror Admins
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 13:07 UTC by ftp
Modified: 2011-11-30 13:50 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 ftp 2011-11-30 13:07:09 UTC
I get the following errors quite often when synchronizing with masterportage.gentoo.org:

1)
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]              
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [Receiver=3.0.7]
2)
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]              
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [Receiver=3.0.7]

This started roughly 16 hours ago.

As a result, the portage data on ftp.halifax.rwth-aachen.de most likely is out of date.
Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2011-11-30 13:16:16 UTC
Hello, I can't reproduce and neither can your peers (see http://mirrorstats.gentoo.org/rsync/#de)

Try checking your route with net-analyzer/mtr (http://www.bitwizard.nl/mtr/) or similar tools.
Comment 2 ftp 2011-11-30 13:26:10 UTC
The route is fine. Manually calling rsync also works most right now. I suspect the problem occurs at x:03 and x:33 every hour?
Comment 3 ftp 2011-11-30 13:32:04 UTC
Reproduced at 14:30:46 CET (a few seconds ago), it worked at 14:30:03 CET. I just noticed the time increased from about 15 seconds (at 14:28) to 31 seconds (at 14:30).
Comment 4 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2011-11-30 13:50:48 UTC
Right. There was some hung processes spinning away cycles.

29678 Nov 30 13:31:01 albatross xinetd[2832]: refused connect from 137.226.34.42       due to excessive load