Hi,

Thanks for the advice! I loosened up the firewall after I noticed an issue with another project we mirror and that resolved the issue there and I thought it might have an effect with CentOS but it appears that's not the case. I can rsync with the official CentOS repo for mirrors so I think my IP should be fine. I checked the access logs and I'm still getting (probably cached) hits to our mirror and the other distros we're mirroring are having zero issues.

I'll wait to see what Fabian says.

Thanks again! Cheers,

Travis

On Thu, May 20, 2021 at 9:25 PM Quantum Mirror root@quantum-mirror.hu wrote:

Hi,

In my opinion this is a routing issue or something is blocking the centos scanner or might be Fabian added a bad IP/host to the scanner (highly unlikely). Check your firewall log, web server log, search for something like "MirrorBrain Probe (see http://mirrorbrain.org/probe_info)" I don't really know the IP(s) or the name (it leaves in the logs) of the CentOS scanner at the moment :( .

And the bonus: (http)mirrorbrain scan be confused - not properly detect timestamp etc.- if you are using special headers - for example fancyindex etc. - with your web server. That's why some distro/project like LO, Kali, arch, GNU use rsync for this task too.

Thats weird, we tried this command: rsync -aqzH --delete *msync.centos.org::CentOS* /mnt/HC_Volume_10038547/public_html/centos And it still failed. But when we try to do the same from other public mirror it works.

By the way I'm not a fan of the -z switch in rsync scripts it can do nasty things sometimes.

Cheers,

Peter

On 2021. 05. 21. 0:42, Travis Newton via CentOS-mirror wrote:

Hello,

I am trying to troubleshoot the issue with our mirror. We noticed that on https://mirror-status.centos.org we have a "no time" status. I've checked and our script is syncing properly. As of this email, TIME and timestamp.txt are both reporting May 20, 2021 17:44 ( https://mirror.nodespace.net/centos/).

What would be causing this? I couldn't really find any useful information searching the mailing list.

Thanks!

Travis

---

CentOS-mirror mailing listCentOS-mirror@centos.orghttps://lists.centos.org/mailman/listinfo/centos-mirror

That was it - looks like our SSL automation forced a redirect to HTTPS. Something else to fix :)

Thanks!

Travis

On Fri, May 21, 2021 at 5:09 AM Fabian Arrotin arrfab@centos.org wrote:

On 21/05/2021 05:15, Travis Newton via CentOS-mirror wrote:

...

Hi,

Thanks for the advice! I loosened up the firewall after I noticed an issue with another project we mirror and that resolved the issue there and I thought it might have an effect with CentOS but it appears that's not the case. I can rsync with the official CentOS repo for mirrors so I think my IP should be fine. I checked the access logs and I'm still getting (probably cached) hits to our mirror and the other distros we're mirroring are having zero issues.

I'll wait to see what Fabian says.

Thanks again! Cheers,

Avij answered already, so if you have 301/302 redirect to *enforce* https, the crawler doesn't follow redirect and so can't reach needed files to verify content

-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror