On 10/29/2014 12:59 PM, Johnny Hughes wrote: > On 10/29/2014 12:26 PM, Martynas UAB "Duomenų Centras" wrote: >> Hello, >> Now for CentOS 6.6 updates don't see our mirror once more... >> >> -----Original Message----- >> From: centos-mirror-bounces at centos.org >> [mailto:centos-mirror-bounces at centos.org] On Behalf Of Fabian Arrotin >> Sent: Tuesday, September 23, 2014 2:09 PM >> To: centos-mirror at centos.org >> Subject: Re: [CentOS-mirror] mirror.duomenucentras.lt >> >> On 18/09/14 10:02, Fabian Arrotin wrote: >>> On 16/09/14 11:48, Martynas UAB Duomen? Centras wrote: >>>> Hello, Noticed that our mirror: mirror.duomenucentras.lt are not >>>> listed in updates repo for centos5, centos6 or centos7 yum clean all; >>>> yum upgrade Loaded plugins: fastestmirror Cleaning repos: >>>> base epel extras updates Cleaning up Everything Loaded plugins: >>>> fastestmirror Determining fastest mirrors epel/metalink | 27 kB >>>> 00:00 * base: mirror.duomenucentras.lt * epel: >>>> mirror.duomenucentras.lt * extras: mirror.duomenucentras.lt * >>>> updates: mirror.skylink-datacenter.de >>>> >>> <snip> >> >>> Hi, >> >>> Sorry for the late answer, but was (and I'm still) busy on some >>> changes for the upcoming 5.11 release. >> >>> Something to keep in mind is that the mirror list that is returned by >>> the mirrorlist nodes are produced by the central mirror checker >>> script. That script verifies each release/arch/repo and it seems that >>> it was thinking your mirror isn't current for the updates repository : >>> http://mirror.duomenucentras.lt/centos/6.5/updates/x86_64/repodata/rep >>> omd.xml >> >> >> error from cache 1410915677 >>> I see that the crawler script is currently running/validating mirrors >>> so let' see. I've though just checked/compared the repomd.xml files >>> and there are correct. >> >>> I'll try to keep an eye on that, but if that doesn't work, feel free >>> to ping me back. >> >>> Cheers, >> >> >> Hi, I verified this morning on the node producing the mirror lists, and >> there was a job that was frozen and so lists for updates repo were generated >> from previously generated cache. >> I've now verified and : >> #curl -4 >> 'http://mirrorlist.centos.org/?repo=updates&release=6&arch=x86_64&cc=lt' >> http://centos.mirror.serveriai.lt/6.5/updates/x86_64/ >> http://mirror.bacloud.com/centos/6.5/updates/x86_64/ >> http://mirror.duomenucentras.lt/centos/6.5/updates/x86_64/ >> http://mirror-pl.kielcetechnologypark.net/centos/6.5/updates/x86_64/ >> http://ftp.prz.edu.pl/centos/6.5/updates/x86_64/ >> http://ftp.ps.pl/pub/Linux/CentOS/6.5/updates/x86_64/ >> http://centos.po.opole.pl/6.5/updates/x86_64/ >> http://centos.hitme.net.pl/6.5/updates/x86_64/ >> http://centos.slaskdatacenter.com/6.5/updates/x86_64/ >> http://centos.komster.pl/6.5/updates/x86_64/ >> >> does that look better now ? >> > > Please remember that mirrorlist picks a number of mirrors from a give > country at random .. and goes to 10 ... if there are are more than 10 > mirrors in a given country, then a given mirror may not show up. > > Each repo gets a random number of mirrors and the mirrorlists are > updated at intervals throught the day (every couple of hours) .. so > updates has different mirrors than os and extras, etc. The actual list > of 10 mirrors is random. > > Once the list of 10 is obtained, then yum uses fastestmirror to rate > those ten mirrors, BUT there is no way to ensure a specific mirror makes > it into the initial random 10. If you want a specific mirror in addition to the mirrorlist, the mirrorlist command and the baseurl command can be used together and you will get 11 mirrors .. and if your mirror is closer and therefore faster, then it will get picked unless it is down for some reason, then the next fastest mirror will be chosen. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-mirror/attachments/20141029/1b152d2f/attachment-0006.sig>