Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 670238 - The Korean mirrors hosted by KAIST (at rsync.kr.gentoo.org, rsync1.kr.gentoo.org, and ftp.kaist.ac.kr) are all down
Summary: The Korean mirrors hosted by KAIST (at rsync.kr.gentoo.org, rsync1.kr.gentoo....
Status: RESOLVED FIXED
Alias: None
Product: Mirrors
Classification: Unclassified
Component: Server Problem (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Mirror Admins
URL: http://www.isitdownrightnow.com/rsync...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-04 02:13 UTC by Chris Slycord
Modified: 2019-03-09 09:03 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 Chris Slycord 2018-11-04 02:13:29 UTC
The Korean mirrors provided by KAIST are down. The machine/IP in question is gentoo's official single rsync mirror as well as a distfile mirror. running "emerge --sync" fails. pinging the URLs leads to the same IP that returns nothing and the "isitdownrightnow" site verifies that it appears offline from their end as well.

[# emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
>>> Starting rsync with rsync://103.22.220.133/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) [Receiver=3.1.3]
>>> Retrying...
!!! Exhausted addresses for rsync.kr.gentoo.org
q: Updating ebuild cache for /usr/portage ...
q: Finished 36046 entries in 0.343227 seconds

Action: sync for repo: gentoo, returned code = 1]

[for x in rsync.kr.gentoo.org rsync1.kr.gentoo.org ftp.kaist.ac
.kr ; do ping -c 10 ${x} ; done
PING rsync.kr.gentoo.org (103.22.220.133) 56(84) bytes of data.

--- rsync.kr.gentoo.org ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 244ms

PING rsync1.kr.gentoo.org (103.22.220.133) 56(84) bytes of data.

--- rsync1.kr.gentoo.org ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 257ms

PING ftp.kaist.ac.kr (103.22.220.133) 56(84) bytes of data.

--- ftp.kaist.ac.kr ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 252ms]

Reproducible: Always

Steps to Reproduce:
1. set "sync-uri = rsync://rsync.kr.gentoo.org/gentoo-portage" in /etc/portage/repos.conf/gentoo.conf
2. emerge --sync
3.
Actual Results:  
sync times out
Comment 1 Alec Warner (RETIRED) archtester gentoo-dev Security 2018-11-04 14:17:23 UTC
https://mirrorstats.gentoo.org/rsync/#kr

I'm going to leave it for a few days as its only been broken for a short while; please use rsync.asia.gentoo.org for now as an alternative.

-A
Comment 2 Chris Slycord 2018-11-04 22:06:29 UTC
It came back online sometime yesterday.
Comment 3 Chris Slycord 2018-11-05 22:35:53 UTC
While I can ping the rsync server, syncing results in "connection refused." So, it's not really totally fixed.

# emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
>>> Starting rsync with rsync://103.22.220.133/gentoo-portage...
>>> Checking server timestamp ...
rsync: failed to connect to 103.22.220.133 (103.22.220.133): Connection refused
(111)
rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3
]
>>> Retrying...
!!! Exhausted addresses for rsync.kr.gentoo.org
q: Updating ebuild cache for /usr/portage ...
q: Finished 36110 entries in 0.857060 seconds

Action: sync for repo: gentoo, returned code = 1
Comment 4 Alec Warner (RETIRED) archtester gentoo-dev Security 2018-11-20 02:13:53 UTC
(In reply to Chris Slycord from comment #3)
> While I can ping the rsync server, syncing results in "connection refused."
> So, it's not really totally fixed.
> 
> # emerge --sync
> >>> Syncing repository 'gentoo' into '/usr/portage'...
> >>> Starting rsync with rsync://103.22.220.133/gentoo-portage...
> >>> Checking server timestamp ...
> rsync: failed to connect to 103.22.220.133 (103.22.220.133): Connection
> refused
> (111)
> rsync error: error in socket IO (code 10) at clientserver.c(127)
> [Receiver=3.1.3
> ]
> >>> Retrying...
> !!! Exhausted addresses for rsync.kr.gentoo.org
> q: Updating ebuild cache for /usr/portage ...
> q: Finished 36110 entries in 0.857060 seconds
> 
> Action: sync for repo: gentoo, returned code = 1

Its up now, again.
Comment 5 Alec Warner (RETIRED) archtester gentoo-dev Security 2019-03-09 09:03:33 UTC
(In reply to Alec Warner from comment #4)
> (In reply to Chris Slycord from comment #3)
> > While I can ping the rsync server, syncing results in "connection refused."
> > So, it's not really totally fixed.
> > 
> > # emerge --sync
> > >>> Syncing repository 'gentoo' into '/usr/portage'...
> > >>> Starting rsync with rsync://103.22.220.133/gentoo-portage...
> > >>> Checking server timestamp ...
> > rsync: failed to connect to 103.22.220.133 (103.22.220.133): Connection
> > refused
> > (111)
> > rsync error: error in socket IO (code 10) at clientserver.c(127)
> > [Receiver=3.1.3
> > ]
> > >>> Retrying...
> > !!! Exhausted addresses for rsync.kr.gentoo.org
> > q: Updating ebuild cache for /usr/portage ...
> > q: Finished 36110 entries in 0.857060 seconds
> > 
> > Action: sync for repo: gentoo, returned code = 1
> 
> Its up now, again.

https://mirrorstats.gentoo.org/rsync/#kr still shows a happy mirror so I'm going to close this out.

-A