[mirror-admin] Blocking ips on dl.fedoraproject.org (Or Please update your mirrors in mirror-manager)
Carlos
carlos at inf.ufpr.br
Mon Mar 28 14:38:17 EDT 2016
Stephen John Smoogen (smooge at gmail.com) wrote on Fri, Mar 25, 2016 at 04:01:26PM BRT:
> uk-noc.com.
> wideopenwest.com.
> alshamil.net.ae.
> ip-connect.net.ua.
> math.uh.edu.
> main.ad.rit.edu.
> mirror.yandex.net.
> pdx.edu.
> unicamp.br.
> sl-reverse.com.
> univ-ubs.fr.
> isp.ip.pt.
> c3sl.ufpr.br.
>
> None of these mirrors are registered in mirrormanager exactly as the
> ip address which is coming.
I don't know how you get these domains but ours is wrong. We are
fedora.c3sl.ufpr.br, not c3sl.ufpr.br, and our IPs are correctly listed in
mirrormanager.
> If that doesn't work we will be putting firewall rules that only Tier 0 and
> Tier 1 mirrors are allowed to connect to the download servers.
Great. This is how it should be. I'm tired of getting "max connections"
rejections...
> Using the last-sync to schedule updates when they actually occur can
> help lower rsync usage.
Certainly. Here's the log from one of these runs:
Usando dl.fedoraproject.org=209.132.181.24
RSYNC_PROTOCOL=30
TEMPO inicializacao: 4s
Mon Mar 28 07:20:05 BRT 2016
TEMPO timestamp upstream: 2s
Mon Mar 28 07:20:07 BRT 2016
upstream_timestamp: Mon Mar 28 07:29:40 UTC 2016
local_timestamp: Mon Mar 28 07:29:40 UTC 2016
TEMPO verificacao de timestamp: 0s
Mon Mar 28 07:20:07 BRT 2016
Timestamp upstream nao e' mais recente
Abortando
The last sentences mean "Timestamp upstream is not more recent [then local
one]. Aborting"
You can see that it takes only a few seconds. All mirrors should check the
timestamp.
--
More information about the Mirror-admin
mailing list