I think my filter was loading all the countries in the block list for some reason. I just reloaded it and not its accurate as shown in the screenshot above.
So, I will just let some time pass and see if the mirror checkers can now reach me.
On Thu, Nov 3, 2016 at 8:17 AM, Brian Lancaster brian@redsox.cc wrote:
I block a several incoming connections from the top 40 spam countries, see list below. Are there any from non-USA IP's that are checking the status of my mirror?
On Thu, Nov 3, 2016 at 7:36 AM, Anssi Johansson centos@miuku.net wrote:
3.11.2016, 6.10, Brian Lancaster kirjoitti:
Can someone tell me what exactly is wrong with the status page in relation to my mirror server?
Its online and current, but showing out of date.
Looking at http://mirror-status.centos.org/ and especially the second graph column, I see that as of this writing, your mirror has been unreachable by the mirror checker for 1.9 days. The "no time" means the mirror checker has been unable to download the timestamp file to verify if it is OK.
Although your mirror seems to be generally reachable (I checked from a few networks), there is at least one network from which I can't connect to your mirror. Here's a traceroute from Gandi:
$ traceroute mirror.redsox.cc traceroute to mirror.redsox.cc (76.211.117.36), 30 hops max, 60 byte packets 1 217.70.191.253 (217.70.191.253) 0.896 ms 0.934 ms 1.003 ms 2 xe0-0-1-2-core4-d.paris.gandi.net (217.70.176.181) 1.159 ms 3.141 ms 3.123 ms 3 10ge8-18.core1.par2.he.net (216.66.89.125) 0.686 ms 0.702 ms 0.685 ms 4 100ge10-1.core1.nyc4.he.net (184.105.81.77) 72.908 ms 72.900 ms 72.876 ms 5 att-internet4-as7018.10gigabitethernet7.switch3.nyc4.he.net (216.66.64.166) 80.528 ms 80.519 ms 80.494 ms 6 cr2.n54ny.ip.att.net (12.122.130.170) 89.038 ms 90.886 ms 90.894 ms 7 cr2.wswdc.ip.att.net (12.122.3.38) 90.870 ms 90.856 ms 91.821 ms 8 cr1.wswdc.ip.att.net (12.122.2.33) 88.701 ms 88.682 ms 88.665 ms 9 cr2.rlgnc.ip.att.net (12.122.2.189) 87.786 ms 89.569 ms 89.544 ms 10 12.123.138.177 (12.123.138.177) 87.126 ms 87.862 ms 87.857 ms 11 * * * 12 * * * 13 99.173.76.179 (99.173.76.179) 90.127 ms 90.158 ms 90.193 ms 14 * * * 15 * * * 16 * * *
On the other hand, traceroutes from "working" networks also stop at 99.173.76.179, so I don't know if this traceroute helps. If you want to do a traceroute to the other direction, try villisika.miuku.net as the target.
"ping mirror.redsox.cc" works from other locations, but not from the host at Gandi. If you can fix your routing so that your mirror will be reachable from that one host at Gandi, perhaps it will also help with the other problem.
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
-- brian@redsox.cc
