[mirror-admin] MirrorManager issue

[Matt Domsch]

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.

For example, the master has:

# ls -l /pub/fedora/linux/updates/18/x86_64/repodata/*prestodelta*
-rw-r--r--. 1 263 mirrors 1009803 Jan 24 18:33
/pub/fedora/linux/updates/18/x86_64/repodata/b99729c4d046010b9fdb50fddb325d816d4d52e0f09b4fc227fa9df73ffb876d-prestodelta.xml.gz

So the crawler tries that:

send: u'HEAD
/fedora/updates/18/x86_64/repodata/b99729c4d046010b9fdb50fddb325d816d4d52e0f09b4fc227fa9df73ffb876d-prestodelta.xml.gz
HTTP/1.1\r\nHost: mirror.nexcess.net\r\nAccept-Encoding: i
dentity\r\nConnection: Keep-Alive\r\nPragma: no-cache\r\nUser-Agent:
mirrormanager-crawler/0.1 (+http://fedorahosted.org/mirrormanager)\r\n\r\n'
reply: 'HTTP/1.1 404 Not Found\r\n'

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 (kernel.org maybe?)
was out of date, and/or your syncing scripts aren't working as expected
(hung, or other).

Thanks,
Matt


On Tue, Jan 22, 2013 at 8:42 AM, Mark McKinstry <mmckinst at nexcess.net>wrote:

> On 01/21/2013 11:39 AM, Mark McKinstry wrote:
>
>> I have a similar problem except my preferred mirror is chosen for
>> everything but updates, regardless of what I tell
>> yum-plugin-fastestmirror and regardless if my IP is on the ASN I've
>> specified in MirrorManager.
>>
>> # release - always at the top
>> https://mirrors.fedoraproject.**org/mirrorlist?repo=fedora-18&**
>> arch=x86_64&ip=208.69.120.1<https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-18&arch=x86_64&ip=208.69.120.1>
>>
>>
>> # updates - never listed
>> https://mirrors.fedoraproject.**org/mirrorlist?repo=updates-**
>> released-f18&arch=x86_64&ip=**208.69.120.1<https://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f18&arch=x86_64&ip=208.69.120.1>
>>
>>
>> Is there a way to see if that is disabled for me too? I've looked around
>> MirrorManager but don't see any settings for it.
>>
>
> 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.
>
> 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
> mirror.nexcess.net ?
>
>
>
> --
> Mark McKinstry
> Nexcess - Beyond Hosting
> 21700 Melrose Ave.
> Southfield, MI  48075
> Phone: +1.866.639.2377
> Fax:   +1.248.281.0473
> http://twitter.com/nexcess
>
> --
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/mirror-admin/attachments/20130124/12613d36/attachment.html>
-------------- next part --------------
--