On Sun, Dec 28, 2014 at 12:06:01PM -0600, MUUG Mirror Manager wrote:
On 14-12-22 01:06 PM, Adrian Reber wrote:
I was confused by the different muug entries. I was looking at the old entry. If you add rsync URLs the crawler can scan the state of your mirror much faster.
Done... but, I notice that I'm getting a lot of 404 errors in my web server logs. All of them are for http://muug.ca/pub/fedora/updates/something. Whereas the directory tree I'm rsync'ing would put the files at http://muug.ca/pub/fedora/linux/updates/something.
Is there some local manipulation required, or have I misunderstood something about mirroring the "enchilada" source?
No, you just entered the wrong path. You should enter:
http://muug.ca/pub/fedora/linux/
The crawler marks your mirror as out of date but as you also are running report_mirror your mirror is marked up to date (because report_mirror with your configuration claims it is up to date). So your mirror is flipping between being marked up to date and not. As long as it is marked as up to date clients are redirected to your mirror and with the information from MirrorManager they are searching for files which do not exist. So, if you update the URL like mentioned above everything should be fine.
If you have rsync running and mention it as a URL in MirrorManager our crawler can use rsync for crawling which is much faster than via http.
What about the mirror ftp.muug.mb.ca. Is this also run by you? Can this be removed?
Adrian