CentOS 6.7 - Yum not detecting update to 6.8

[gdsavage]

Hello! I'm running 2 basic web servers, one is the Production server and one is the Failover server. As you can probably guess, the servers were set up to be as similar as possible (although I wasn't involved in their creation), and the Failover server receives copies of the Production site files and databases on a regular cron job. We have Failover set up to auto-update, but we update Production manually on a regular basis (bi-weekly at the very least, or asap when an important security fix is released).

This morning I intended on updating both servers from 6.7 to 6.8, and decided to try it out on the Failover server first. I ran a simple yum update on Failover, it ran like a charm, and the server is now happily reporting in as CentOS 6.8 (which I verified with cat /etc/*elease).

When I attempt the same yum update on Production, all I get is No Packages marked for Update. I tried running yum clean all thinking it might be a caching issue, but there was no change. I noticed the release notes mentioned that the yum update should run fine if you didn't mess with the default configuration too much, so I compared both servers' configuration at /etc/yum.conf and they are identical.

The last thing I checked was differences in the repolist on each server with yum repolist. There are some minor differences here, but my guess is that is because they are now running different versions of CentOS

Production Repolist

Code: Select all

Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * epel: linux.mirrors.es.net
repo id			repo name								status
base				CentOS-6 - Base							6,575
epel				Extra Packages for Enterprise Linux 6 - x86_64	12,146
extras			CentOS-6 - Extras						64
updates			CentOS-6 - Updates						1,622
repolist: 20,407

Failover Repolist

Code: Select all

Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
repo id			repo name								status
base				CentOS-6 - Base							6,696
epel				Extra Packages for Enterprise Linux 6 - x86_64	12,145
extras			CentOS-6 - Extras						62
rackspace			Rackspace Monitoring					1
updates			CentOS-6 - Updates						94
repolist: 18,998

Does anyone have any suggestions? I'd like to avoid doing a fresh install on the Production server if at all possible, so I'm hoping there is something I can do to get the yum update behaving the way I'm expecting. Thanks in advance!

[gerald_clark]

Show the contents of your /etc/yum.repos.d/CentOS-Base.repo file.

[gdsavage]

Aha! I think you've found the culprit gerald_clark It looks like the Servint (Production host) repos are lagging a little behind the Rackspace (Failover host) ones. So could the fix be as simple as uncommenting the mirrorlist value(s), commenting out the baseurl value(s), and re-running the update?

cat /etc/yum.repos.d/CentOS-Base.repo

# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client. You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
#mirrorlist=http://mirrorlist.centos.org/?release=$ ... ch&repo=os
baseurl=http://ftp.servint.net/linux/centos64/$releasever/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#released updates
[updates]
name=CentOS-$releasever - Updates
#mirrorlist=http://mirrorlist.centos.org/?release=$ ... po=updates
baseurl=http://ftp.servint.net/linux/centos64/u ... eleasever/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
#mirrorlist=http://mirrorlist.centos.org/?release=$ ... epo=extras
baseurl=http://ftp.servint.net/linux/centos64/e ... eleasever/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
#mirrorlist=http://mirrorlist.centos.org/?release=$ ... centosplus
baseurl=http://ftp.servint.net/linux/centos64/c ... eleasever/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
#mirrorlist=http://mirrorlist.centos.org/?release=$ ... po=contrib
baseurl=http://ftp.servint.net/linux/centos64/c ... eleasever/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

[gerald_clark]

That is not a correct repo file.
It is pointing to an old private repo for 6.4.
Compare it to the other machine.

[gdsavage]

That is not a correct repo file.
It is pointing to an old private repo for 6.4.
Compare it to the other machine.

Yea, the Failover machine is pointing to Rackspace private repos, which seem to be more up-to-date. Adding on to the question from my previous post: should I just change the baseurl value to use the Rackspace repos (even though it's not a Rackspace machine), or would using the mirrorlist values automatically find the best (and closest) repo for my Production machine to use?

[gerald_clark]

They will try to get you a close fast repo.

[gdsavage]

Commenting out all of the baseurl values and uncommenting all of the mirrorlist values in /etc/yum.repos.d/CentOS-Base.repo worked perfectly. Thanks for the quick assist!

[gerald_clark]

You are welcome.