With that information, here was the projected start and end states.Start state: Red Hat Enterprise Linux Server release 6.0 (Santiago) My SQL 5.1.47 Projected end state: Red Hat Enterprise Linux Server release 6.4 (Santiago) My SQL Community Server 5.5.34 One hitch was that the latest version of My SQL available from any of the official Red Hat repositories is My SQL 5.1.69.Since the official Red Hat repositories didn’t offer what we needed, we needed to identify a third-party repository that we could trust.Fortunately, there was one available that we had used before and trusted – Les RPM de Remi Les RPM de Remi is a popular RPM repository for LAMP and one of its stated goals is “providing the latest versions of the LAMP stack, and some other software, to the Fedora and Enterprise Linux (RHEL, Cent OS, Oracle, Scientific Linux, …) users.” Remi had My SQL 5.5.34 Community Server available, so we could use this repository to update our existing My SQL installation.A subscription service has the role to identify registered systems with the products installed on them.Local Subscription Manager service tracks down the installed software products, available and used subscriptions and communicates with the Red Hat Customer Portal through tools like YUM.In order to upgrade to My SQL 5.5, we had two options: compile from source code, or find an third-party repository offering the necessary My SQL RPMs.
NOTE: After the system is successfully authenticated an ID will be displayed on your prompt for your system. To unregister your system use unregister switch, which will remove the system’s entry from the subscription service and all subscriptions, and will deletes its identity and subscription certificates on local machine. To active it a subscription use the Subscription Pool ID, but be aware that when purchase one, it is valid for a specified period of time, so make sure you buy a new period of time before expiring.However, I looked ahead to Casper 9.x and saw the following versions of My SQL were now listed as being required: My SQL Enterprise Edition 5.5 or later, or My SQL Community Server 5.5 or later I’m still running Casper 8.x, but I wanted to get ahead of the curve and not have to deal with a My SQL upgrade at the same time as a future Casper 9.x upgrade.Thanks to the Linux folks at my workplace, I was able to do so with a minimum of hassle. When I checked with my colleague Peter Bukowinski, it became apparent that RHEL would need to be upgraded as well in order to support My SQL 5.5.x.NOTE: Here I’ve enabled RHEL 7 Server Optional RPMs repositories which I will need later to install some important PHP moduleson a LAMP server. After you edited the file and enabled all your needed Repositories using the procedure above, run yum repolist all or just yum repolist, again to verify repos status like in the screenshots below. After everything concerning subscriptions and repositories has been set, upgrade your system to make sure your system has the latest packages, kernels and security patches up to date, issuing the following command. Now your system is up to date and you can start perform other important task like starting to build a complete web environment for productions by installing all the necessary software packages, which will be covered in future tutorials.All our production servers run Red Hat Enterprise Linux (RHEL) 5 with the system supplied packages for the majority of applications we run, with the exception of PHP which we have a custom compiled version.