OnApp: Update Packages after CentOS 5.x EoL
As part of our Server Virtualization Technologies and Services, we assist our customers with several OnApp queries.
Today, let us see how to update packages
OnApp: Update Packages after CentOS 5.x EoL
Since centos.org stopped the support of CentOS 5.x, the update of packages using default repositories is no longer applicable.
So we need to switch the boxes run on CentOS 5.x., to so-called Vault repositories.
Doing so will give a possibility to install packages that are necessary because of different dependencies.
Moving ahead, let us see how our Support Techs switch to the Vault repository.
To do so, we disable base, updates, and other enabled repositories (where enabled=1 is set) in the CentOS-Base.repo:
# sed -i ‘s/enabled=1/enabled=0/g’ /etc/yum.repos.d/CentOS-Base.repoThen check the /etc/yum.repos.d/CentOS-Base.repo, and upend ‘enabled=0’ into every repository with no ‘enabled’ option.
After that, we enable c5.11-base and c5.11-updates:
#vim /etc/yum.repos.d/CentOS-Vault.repo
Eventually, we append to the file or edit if it exists (set enabled=1) c5.11-base and c5.11-updates repositories:
[c5.11-base] gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5 gpgcheck=1 name=CentOS-5.11 – Base baseurl=http://vault.centos.org/5.11/os/$basearch/ exclude=ruby* libyaml* corosync* corosynclib* pacemaker* enabled=1
[c5.11-updates]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5 gpgcheck=1 name=CentOS-5.11 – Updates baseurl=http://vault.centos.org/5.11/updates/$basearch/ exclude=ruby* libyaml* corosync* corosynclib* pacemaker* enabled=1
[Stuck in between? We are available 24*7]
Conclusion
To conclude, in order to update the Packages after CentOS 5.x EoL we switch boxes, run on CentOS 5.x., to Vault repositories. Today, we saw how our Support Techs perform the same for our customers.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
0 Comments