On Sat, May 12, 2018 at 01:56:29PM +0800, Shengjing Zhu wrote:
On Wed, May 9, 2018 at 8:26 PM, Adrian Reber <adrian(a)lisas.de>
wrote:
>
> Thanks for having a closer look. Just also talked with a USTC mirror
> admin on IRC.
>
> USTC is wrongly configured in mirrormanager, basically all paths
> configured are pointing to non existing directories on the mirror. They
> specify
https://mirrors.ustc.edu.cn/fedora/linux as the root URL for
> their Fedora mirror which returns 404. The URL for EPEL is also wrong.
>
In last talk on IRC, this is not the root the cause of the problem.
Few days ago, the old mirror site was deleted. I also tried to use
quick-fedora-mirror to sync fedora-secondary and epel. The checkin was
successful several times.
But I still can't see USTC appeared in the mirror list. P.S. I tested
from university IP I configured in "Site-local Netblocks"
When I'm writing,
https://mirrors.fedoraproject.org/metalink?repo=fedora-27&arch=aarch6...
result is empty.
The FILTEREXP I configured for fedora-secondary is
'(/s390/|/s390x/|/ppc64le/|/ppc64/|/source|/SRPMS|/debug/|/releases/test|/updates/testing|/development/)',
I'm not sure if this matters.
Not really sure what is happening. Currently I assume that your
report_mirror is not working correctly. Is FILTEREXP from
quick-fedora-mirror? Or are you using report_mirror the stand-alone
python tool. It would be interesting to see what the server answers when
you run report_mirror.
My current theory is, your report_mirror config is not correct and
deletes all directories listed as up to date from your mirror in
MirrorManager. Once the crawler scans your mirror it is updated
correctly again. So the state of the mirror flips between crawling and
report_mirror.
Adrian