On Mon, May 14, 2018 at 1:56 AM, Adrian Reber <adrian(a)lisas.de> wrote:
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.
FILTEREXP is from quick-fedora-mirror. I'm not using the stand alone
report_mirror. I'm using quick-fedora-mirror to checkin.
I didn't see this zsh version has useful log.
Anyway the log is attached at:
http://ftp.ustclug.org/~zsj/logs/fedora-secondary.log.txt
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.
I think when the check is finished,
the "Up-to-Date Directories this host carries" on
https://admin.fedoraproject.org/mirrormanager/host/2266/category/7937
is correct. Maybe the crawler is the reason the site is marked as not
update2date?
--
Linux User Group
University of Science and Technology of China
Homepage:
https://lug.ustc.edu.cn/
E-Mail: lug(a)ustc.edu.cn
Shengjing Zhu <zhsj(a)ustclug.org>