[mirror-admin] EPEL "freshness"

[Matt_Domsch at Dell.com]

I think this is working as expected.

The crawler recognized previous content was current on your mirror during the crawl between
Starting crawl 2010-05-14T19:21:14.711732
Ending crawl 2010-05-14T19:27:26.432709


The file changed at
Fri May 14 19:51:57 UTC 2010

The update-master-directory-server run started at
Starting umdl 2010-05-14T20:30:07.250389
and noticed the new content on the master at
pub/epel/testing/5/x86_64/repodata has changed
Ending umdl 2010-05-14T21:59:00.038854

Then you were crawled at
Starting crawl 2010-05-14T21:21:33.847178
and it noticed you weren't up-to-date anymore
Directory pub/epel/5/x86_64/repodata is not up-to-date on this host.

You say your log showed you downloaded it at 20:45 CDT, 01:45 UTC, but this seems late to me, because on the next crawler run:

You were then crawled at
Starting crawl 2010-05-14T23:22:11.516608
Which saw the new version.


--
Matt Domsch
Technology Strategist
Dell | Office of the CTO


-----Original Message-----
From: mirror-list-d-bounces at redhat.com [mailto:mirror-list-d-bounces at redhat.com] On Behalf Of Chris Adams
Sent: Friday, May 14, 2010 5:45 PM
To: mirror-list-d at redhat.com
Subject: EPEL "freshness"

I saw that my mirror (mirror.hiwaay.net) dropped out of the EPEL mirror
lists.  I checked the log (thanks Matt!) and see that the last scan
showed my EPEL directories as out of date.

I checked my web logs for the scan time, and among the files I see the
crawler tried to get was:

/pub/epel/testing/5/x86_64/repodata/294e179903379c50ac1594e83dabdb4e63527659-other.xml.gz

I checked my mirror logs, and I downloaded that file yesterday at about
20:45 (CDT), and deleted it today at 16:05 as it was replaced by a newer
version.

It appears that the crawler is checked against an out-of-date copy
itself.
-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

--

--