<div dir="ltr">It's crawling them, but not finding up-to-date content. For example, your updates/18/x86_64/repodata directory has content from Jan 14, but not newer.<div><br></div><div style>For example, the master has:</div>
<div><br></div><div><div># ls -l /pub/fedora/linux/updates/18/x86_64/repodata/*prestodelta*</div><div>-rw-r--r--. 1 263 mirrors 1009803 Jan 24 18:33 /pub/fedora/linux/updates/18/x86_64/repodata/b99729c4d046010b9fdb50fddb325d816d4d52e0f09b4fc227fa9df73ffb876d-prestodelta.xml.gz</div>
</div><div><br></div><div style>So the crawler tries that:</div><div><br></div><div><div>send: u'HEAD /fedora/updates/18/x86_64/repodata/b99729c4d046010b9fdb50fddb325d816d4d52e0f09b4fc227fa9df73ffb876d-prestodelta.xml.gz HTTP/1.1\r\nHost: <a href="http://mirror.nexcess.net">mirror.nexcess.net</a>\r\nAccept-Encoding: i</div>
<div>dentity\r\nConnection: Keep-Alive\r\nPragma: no-cache\r\nUser-Agent: mirrormanager-crawler/0.1 (+<a href="http://fedorahosted.org/mirrormanager">http://fedorahosted.org/mirrormanager</a>)\r\n\r\n'</div><div>reply: 'HTTP/1.1 404 Not Found\r\n'</div>
</div><div><br></div><div style>Yep, it's 404. Your copy of the content is from Jan 14, which is old enough (> 3 days) that MM won't go looking for it, allowing for a slightly stale mirror but not 10 days stale. So your upstream (<a href="http://kernel.org">kernel.org</a> maybe?) was out of date, and/or your syncing scripts aren't working as expected (hung, or other).</div>
<div><br></div><div style>Thanks,<br></div><div style>Matt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 22, 2013 at 8:42 AM, Mark McKinstry <span dir="ltr"><<a href="mailto:mmckinst@nexcess.net" target="_blank">mmckinst@nexcess.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 01/21/2013 11:39 AM, Mark McKinstry wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a similar problem except my preferred mirror is chosen for<br>
everything but updates, regardless of what I tell<br>
yum-plugin-fastestmirror and regardless if my IP is on the ASN I've<br>
specified in MirrorManager.<br>
<br>
# release - always at the top<br>
<a href="https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-18&arch=x86_64&ip=208.69.120.1" target="_blank">https://mirrors.fedoraproject.<u></u>org/mirrorlist?repo=fedora-18&<u></u>arch=x86_64&ip=208.69.120.1</a><br>
<br>
<br>
# updates - never listed<br>
<a href="https://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f18&arch=x86_64&ip=208.69.120.1" target="_blank">https://mirrors.fedoraproject.<u></u>org/mirrorlist?repo=updates-<u></u>released-f18&arch=x86_64&ip=<u></u>208.69.120.1</a><br>
<br>
<br>
Is there a way to see if that is disabled for me too? I've looked around<br>
MirrorManager but don't see any settings for it.<br>
</blockquote>
<br></div>
Looking at the crawler log in MirrorManager, it isn't crawling the updates directory for Fedora 16, 17, or 18 at all which probably explains why the mirror is never used for updates. It also isn't showing any errors for them.<br>
<br>
I don't see any setting that controls this. Is there some other setting that is causing it not to crawl all the updates directory for <a href="http://mirror.nexcess.net" target="_blank">mirror.nexcess.net</a> ?<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
-- <br>
Mark McKinstry<br>
Nexcess - Beyond Hosting<br>
21700 Melrose Ave.<br>
Southfield, MI 48075<br>
Phone: <a href="tel:%2B1.866.639.2377" value="+18666392377" target="_blank">+1.866.639.2377</a><br>
Fax: <a href="tel:%2B1.248.281.0473" value="+12482810473" target="_blank">+1.248.281.0473</a><br>
<a href="http://twitter.com/nexcess" target="_blank">http://twitter.com/nexcess</a><br>
<br>
--<br>
<br>
</div></div></blockquote></div><br></div>