[CentOS-mirror] New Mirror

Sat Nov 26 08:49:31 UTC 2016
Anssi Johansson <centos at miuku.net>

24.11.2016, 20.16, LiteHost - Cheap SSD 10gbps servers kirjoitti:
> Hello,
>
> I want to setup my first mirror of centos.
>
> HTTP: http://centos.chicago.litehost.co/

Hi, looks like your mirror has some performance problems on IPv6. When I 
run my manual IPv6 mirror checking script, I get this:

Checking http://centos.chicago.litehost.co/
IPV6: 2001:49f0:6000:405:0:0:0:3
http://centos.chicago.litehost.co/5/updates/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/fasttrack/i386/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/5/fasttrack/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/cr/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/centosplus/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/os/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/extras/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/contrib/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/addons/i386/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/5/addons/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/updates/i386/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/6/updates/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/fasttrack/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/cr/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/centosplus/i386/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/6/centosplus/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/os/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/extras/i386/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/6/extras/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/6/contrib/i386/repodata/repomd.xml
http://centos.chicago.litehost.co/5/updates/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/fasttrack/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/cr/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/centosplus/x86_64/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/5/centosplus/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/os/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/extras/x86_64/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/5/extras/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/contrib/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/5/addons/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/6/updates/x86_64/repodata/repomd.xml
repomd.xml is old
http://centos.chicago.litehost.co/6/fasttrack/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/6/cr/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/6/centosplus/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/6/os/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/6/extras/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/6/contrib/x86_64/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/6/contrib/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/7/centosplus/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/7/cr/x86_64/repodata/repomd.xml
repomd.xml is old
http://centos.chicago.litehost.co/7/extras/x86_64/repodata/repomd.xml
repomd.xml failed at 
http://centos.chicago.litehost.co/7/extras/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/7/fasttrack/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/7/os/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/7/updates/x86_64/repodata/repomd.xml
http://centos.chicago.litehost.co/ : FAIL

The "repomd.xml is old" messages are fairly harmless, but the 
"repomd.xml failed" messages say the script was unable to download the 
file. When I run the same script again, the list of failed downloads 
will be different. I would suggest having a look at this problem before 
the actual mirror traffic hits your mirror. Perhaps there is some sort 
of a firewall that limits incoming requests? Doing the same test over 
IPv4 seems to work OK.