Hello Johnny,
That appears to be it, our network DNS resolvers were caching an old record
from the looks of it.
I've cleared the cache, and everything is now working perfectly.
Thank you (all) for the help, I wasn't even aware that the 204.15.73.243
address was no longer valid.
On 21 October
On 10/20/2015 01:28 PM, Jonathan Billings wrote:
> On Tue, Oct 20, 2015 at 12:29:06PM -0500, Johnny Hughes wrote:
>> Those 3 addresses are good, the 204.15.73.243 is incorrect.
>
> 204.15.73.243 reverse resolves to centos.at.multacom.com.
> multacom is a CentOS Sponsor according to:
> https://www.
On Tue, Oct 20, 2015 at 12:29:06PM -0500, Johnny Hughes wrote:
> Those 3 addresses are good, the 204.15.73.243 is incorrect.
204.15.73.243 reverse resolves to centos.at.multacom.com.
multacom is a CentOS Sponsor according to:
https://www.centos.org/sponsors/
An outdated config somewhere?
--
Jon
On 10/19/2015 06:18 PM, John Cenile wrote:
> I'm actually not able to connect to that host:
>
> # curl "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=extras";
> curl: (7) couldn't connect to host
>
>
> Which lead me to discover that our entire network is picking up "
> mirrorlist.cent
I'm actually not able to connect to that host:
# curl "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=extras";
curl: (7) couldn't connect to host
Which lead me to discover that our entire network is picking up "
mirrorlist.centos.org" as 204.15.73.243, which I'm not able to ping from
a
On 10/19/2015 06:49 AM, John Cenile wrote:
> Thanks for the suggestions, unfortunately that file doesn't exist.
>
> I'm very confused as to why it's trying to download from /6.6/.
>
> The output of rpm -qi centos-release-6-4.el6.centos.10.x86_64 is:
>
> Name: centos-release
Sorry, I just copied any line from the repo file. :)
On 19 October 2015 at 22:39, Nicolas Thierry-Mieg <
nicolas.thierry-m...@imag.fr> wrote:
> On 10/19/2015 07:20 AM, John Cenile wrote:
>
>> Hello Clint,
>>
>> Our Centos-base.repo file looks like this:
>>
>> [base]
>> name=CentOS-$releasever - B
Thanks for the suggestions, unfortunately that file doesn't exist.
I'm very confused as to why it's trying to download from /6.6/.
The output of rpm -qi centos-release-6-4.el6.centos.10.x86_64 is:
Name: centos-release Relocations: (not relocatable)
Version : 6
On 10/19/2015 07:20 AM, John Cenile wrote:
Hello Clint,
Our Centos-base.repo file looks like this:
[base]
name=CentOS-$releasever - Base
mirrorlist=
http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgche
John Cenile wrote:
I have tried yum clean all multiple times, no luck. :(
Also check you don't have the file /etc/yum/vars/releasever - the
contents of this will override the value of $releasever in the repo files
James Pearson
___
CentOS mailing
On Mon, 19 Oct 2015, John Cenile wrote:
I have tried yum clean all multiple times, no luck. :(
Any other ideas?
Have you manually set releasever in your yum config?
As a short term fix, maybe you should.
jh
___
CentOS mailing list
CentOS@centos.or
I have tried yum clean all multiple times, no luck. :(
Any other ideas?
On 19 October 2015 at 18:01, James Pearson
wrote:
> >
> > On 19 Oct 2015, at 04:22, "John Cenile" wrote:
> >
> > When performing a yum update, it fails because it's trying to download
> from:
> >
> > mirror.centos.org/cent
>
> On 19 Oct 2015, at 04:22, "John Cenile" wrote:
>
> When performing a yum update, it fails because it's trying to download from:
>
> mirror.centos.org/centos/*6.6*/extras/x86_64/repodata/repomd.xml
>
> Which fails due to the fact that the entire 6.6 directory is empty on all
> of the mirror
Hello Clint,
Our Centos-base.repo file looks like this:
[base]
name=CentOS-$releasever - Base
mirrorlist=
http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-K
On 10/18/2015 8:21 PM, John Cenile wrote:
Which fails due to the fact that the entire 6.6 directory is empty on all
of the mirrors I have checked.
isn't 6.7 out ? why would there be anything left in 6.6 ?
--
john r pierce, recycling bits in santa cruz
On Mon, Oct 19, 2015 at 4:21 PM, John Cenile wrote:
> Hello all,
>
> I manage a few servers overseas that are running CentOS 6.
>
> When performing a yum update, it fails because it's trying to download
> from:
>
> mirror.centos.org/centos/*6.6*/extras/x86_64/repodata/repomd.xml
>
>
> Which fails
Hello all,
I manage a few servers overseas that are running CentOS 6.
When performing a yum update, it fails because it's trying to download from:
mirror.centos.org/centos/*6.6*/extras/x86_64/repodata/repomd.xml
Which fails due to the fact that the entire 6.6 directory is empty on all
of the m
17 matches
Mail list logo
