Anssi Johansson kirjoitti: > Hi, I noticed that there are a number of broken rsync URLs on the CentOS > mirror list. Perhaps the directory names have been changed over time, > and nobody told the CentOS mirror maintainers of the changes. > > Here's a list of the URLs and my suggestions for the replacements: > > OLD: rsync://centos.mirror.lstn.net/ > NEW: rsync://centos.mirror.lstn.net/centos/ > > OLD: rsync://ftpmirror.your.org/pub/centos/ > NEW: rsync://ftpmirror.your.org/centos/ > > OLD: rsync://linux.mirrors.es.net/linux-pub/ > NEW: rsync://linux.mirrors.es.net/centos/ > > OLD: rsync://mirror.as24220.net/pub/centos/ > NEW: rsync://mirror.as24220.net/centos/ > > OLD: rsync://mirrors.syringanetworks.net/centos/ > NEW: rsync://mirrors.syringanetworks.net/CentOS/ > > OLD: rsync://rsync.nic.funet.fi/pub/mirrors/centos.org/ > NEW: rsync://rsync.nic.funet.fi/ftp/pub/mirrors/centos.org/ > > OLD: rsync://ftp.nluug.nl/CentOS/ > NEW: rsync://ftp.nluug.nl/centoslinux/ > > OLD: rsync://stingray.cyber.net.pk/pub/centos/ > NEW: rsync://stingray.cyber.net.pk/centos/ > Thank you for your overwhelming feedback regarding my previous message to the mailing list. If you need to leave this mailing list, please click the link at the bottom of this email and see the "To unsubscribe from CentOS-mirror.." option at the bottom of that page. Any messages sent to the centos-mirror mailing list address will be sent to ALL the subscribers of this mailing list. If your message doesn't need to be seen by all the hundreds of subscribers of this list, please consider sending your reply directly to the sender of the message instead of sending it to the mailing list. Thank you for your understanding. Back to business. I had somehow thought that only the rsync URLs are not checked automatically by the IPv4 mirror checking scripts. However, this may not be entirely accurate. It appears that if there's also an HTTP URL specified for the mirror, only the HTTP URL is checked and not the FTP URL. Thus it may be possible that some FTP URLs have become stale over time and those problems are not detected by the mirror checking scripts. I had a look at the FTP URLs, and noticed problems with the following mirrors: ftp://be.mirror.eurid.eu/centos/ ftp://centos.mirror.lstn.net/ ftp://centos.mirror.nucleus.be/ ftp://centos.supsec.org/pub/linux/centos/ ftp://ftp.cica.es/CentOS/ ftp://ftp.nsysu.edu.tw/CentOS/ ftp://ftp.sunet.se/pub/Linux/distributions/centos/ ftp://ftp.tc.edu.tw/Linux/Centos/ ftp://mirror.quintex.com/centos/ ftp://mirror.root.lu/centos/ ftp://mirror.sov.uk.goscomb.net/centos/ ftp://mirror.telepoint.bg/centos/ ftp://mirror.ufs.ac.za/os/linux/distros/centos/ ftp://mirror.yandex.ru/centos/ ftp://mirror.yourwebhoster.eu/centos/ ftp://mirrors.arsc.edu/centos/ ftp://mirrors.gigenet.com/centos/ ftp://nl.mirror.eurid.eu/centos/ ftp://stingray.cyber.net.pk/pub/centos/ This time I did the testing primarily over IPv4. Some of those mirrors seem to fail when trying to use the passive protocol, but work fine when using the active protocol (assuming the client's firewall is configured to allow such inbound connections). More details of my testing are presented below. ftp://be.mirror.eurid.eu/centos/ PASV ... couldn't connect to 78.41.71.17 port 37248: Connection timed out ** Note: Using active FTP mode works for this server ftp://centos.mirror.lstn.net/ No such file `TIME'. ** Note: New URL ftp://centos.mirror.lstn.net/centos/ ftp://centos.mirror.nucleus.be/ Connecting to centos.mirror.nucleus.be|31.193.177.85|:21... failed: Connection refused. ** Note: Connections to the FTP port over IPv6 fail similarly ftp://centos.supsec.org/pub/linux/centos/ Resolving centos.supsec.org... 208.209.50.19, 208.209.50.16, 208.209.50.18 Connecting to centos.supsec.org|208.209.50.19|:21... failed: Connection timed out. Connecting to centos.supsec.org|208.209.50.16|:21... failed: Connection timed out. Connecting to centos.supsec.org|208.209.50.18|:21... failed: Connection timed out. Giving up. ftp://ftp.cica.es/CentOS/ PASV ... couldn't connect to 150.214.5.134 port 22195: Connection timed out ftp://ftp.cica.es/CentOS/ with --no-passive: ==> PORT ... done. ==> RETR TIME ... Error in server response, closing control connection. (tcpdump says: "OOPS: vsf_sysutil_recv_peek: no data" and "child died") ** Note: I didn't see any connection attempts with tcpdump to the TCP port specified by the client ftp://ftp.nsysu.edu.tw/CentOS/ No such directory `CentOS'. ** Note: New URL ftp://ftp.nsysu.edu.tw/Unix-like/CentOS/ ftp://ftp.sunet.se/pub/Linux/distributions/centos/ in active mode, passive mode works: ==> PORT ... done. ==> RETR TIME ... Error in server response, closing control connection. ** Note: There seems to be some sort of a firewall config problem. ftp.sunet.se sends a SYN, my server accepts it, but ftp.sunet.se doesn't seem to get my reply. ftp://ftp.tc.edu.tw/Linux/Centos/ No such directory `Linux/Centos'. ** Note: New URL ftp://ftp.tc.edu.tw/Linux/CentOS/ ftp://mirror.quintex.com/centos/ Connecting to mirror.quintex.com|199.249.223.98|:21... failed: Connection timed out. ** Note: Connections to the FTP port over IPv6 fail similarly ftp://mirror.root.lu/centos/ No such file `TIME'. ** Note: All the directories seem to be empty ftp://mirror.sov.uk.goscomb.net/centos/ PASV ... couldn't connect to 77.75.110.242 port 63055: Connection timed out ** Note: Using active FTP mode works for this server ftp://mirror.telepoint.bg/centos/ Connecting to mirror.telepoint.bg|79.124.67.90|:21... failed: Connection refused. ** Note: Connections to the FTP port over IPv6 fail similarly ftp://mirror.ufs.ac.za/os/linux/distros/centos/ Connecting to mirror.ufs.ac.za|146.182.9.30|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /os/linux/distros/centos ... done. ==> SIZE TIME ... 11 ==> PASV ... couldn't connect to 146.182.9.30 port 35716: No route to host ** Note: Using active FTP mode works for this server ftp://mirror.yandex.ru/centos/ in active mode, passive mode works: ==> PORT ... done. ==> RETR TIME ... Error in server response, closing control connection. ** Note: There seems to be some sort of a firewall config problem. mirror.yandex.ru does not send SYNs to the client. ftp://mirror.yourwebhoster.eu/centos/ Connecting to mirror.yourwebhoster.eu|178.21.23.188|:21... connected. Logging in as anonymous ... Login incorrect. ** Note: This is supposed to be a public mirror, right? ftp://mirrors.arsc.edu/centos/ Connecting to mirrors.arsc.edu|199.165.82.202|:21... failed: Connection refused. ** Note: Connections to the FTP port over IPv6 fail similarly ftp://mirrors.gigenet.com/centos/ Connecting to mirrors.gigenet.com|69.65.15.34|:21... failed: Connection refused. ** Note: Connections to the FTP port over IPv6 times out ftp://nl.mirror.eurid.eu/centos/ PASV ... couldn't connect to 130.117.72.247 port 32631: Connection timed out ** Note: Using active FTP mode works for this server ftp://stingray.cyber.net.pk/pub/centos/ No such directory `pub/centos' ** Note: New URL ftp://stingray.cyber.net.pk/centos/ All the other FTP servers worked fine in both active and passive mode. If you're the admin of any of those mirrors, please take appropriate action. It'd be nice if Ralph could change the changed URLs to the CentOS mirror database. This would shorten the list of "unreachable mirrors" list on http://miuku.net/ipv6reach/ -- thanks for your time :)