Complete Guide to Upgrading PHP from 5.3 to 5.6 on CentOS 6.5

Background Analysis of PHP Upgrade on CentOS 6.5

In CentOS 6.5 systems, the default PHP version is 5.3.3, which is indeed a relatively outdated version. When users attempt to upgrade using the yum update command, the system displays "No Packages marked for Update". This is not an operational error but rather a limitation of the CentOS official repository policy.

As an enterprise-grade Linux distribution, CentOS prioritizes stability over having the latest software versions. Even though PHP 5.3.3 was initially released in 2010, the CentOS team repackaged it in 2013, primarily to backport critical security fixes and bug patches. This conservative update strategy ensures production environment stability but proves insufficient for development environments requiring new features.

Detailed Webtatic Repository Upgrade Solution

To overcome official repository limitations, we need to introduce third-party repositories. The Webtatic repository provides a reliable solution with the following specific upgrade steps:

First, add the Webtatic repository to the system:

rpm -Uvh http://mirror.webtatic.com/yum/el6/latest.rpm

This command downloads and installs the Webtatic repository configuration files, enabling the system to access updated PHP packages.

Next, dependency conflicts must be addressed. Due to incompatibility between old and new PHP version components, the old php-common package must be removed first:

yum remove php-common

This step is crucial. Skipping it and directly installing the new version will result in package conflict errors.

Then install PHP 5.6 core packages and common extensions:

yum install php56w
yum install php56w-mysql
yum install php56w-common
yum install php56w-pdo
yum install php56w-opcache

The specific functions of each command are as follows: php56w is the PHP 5.6 core package providing basic PHP functionality; php56w-mysql provides MySQL database connection support; php56w-common contains shared library files and configuration files; php56w-pdo is the PHP Data Objects extension offering unified database access interface; php56w-opcache is the opcode cache extension that significantly improves PHP performance.

After installation completes, verify the version upgrade success:

php --version

Normally, the output should display PHP 5.6.x version information, confirming successful upgrade.

In-depth Analysis of Dependency Issues and Solutions

Various dependency issues may arise during the upgrade process, particularly when attempting to upgrade to higher versions like PHP 7.x. The dependency errors mentioned in the reference article are typical:

Error: Package: php-7.2.10-1.el6.remi.x86_64 (remi-php72)
Requires: libgssapi_krb5.so.2()(64bit)
Error: Package: php-7.2.10-1.el6.remi.x86_64 (remi-php72)
Requires: libdl.so.2(GLIBC_2.2.5)(64bit)
Error: Package: php-cli-7.2.10-1.el6.remi.x86_64 (remi-php72)
Requires: libcrypt.so.1()(64bit)

These errors indicate the system lacks necessary shared library files. In CentOS 6 environments, the GLIBC (GNU C Library) version is too old to meet newer PHP version dependency requirements. In such cases, upgrading to PHP 5.6 is a more feasible choice since its dependency requirements have better compatibility with CentOS 6 base libraries.

If PHP 7.x versions are absolutely necessary, consider upgrading the operating system to CentOS 7 or newer versions, as CentOS 6 base library versions genuinely cannot meet modern software requirements.

Safe Rollback Mechanism

Any system upgrade carries risks, thus a comprehensive rollback plan must be prepared. If compatibility issues arise after upgrade, recovery can be performed following these steps:

sudo yum remove php56w
sudo yum remove php56w-common
sudo yum install php-common
sudo yum install php-mysql
sudo yum install php

This rollback process first removes the newly installed PHP 5.6 packages, then reinstalls the original PHP components. Note that rollback may lose PHP configuration file modifications made during upgrade, so backing up important configuration files before upgrading is recommended.

Third-party Repository Selection Strategy

Besides the Webtatic repository, the Remi repository is another common choice. Both repositories have their advantages: Webtatic repository has simple configuration and clear package categorization; Remi repository has more timely version updates and supports more PHP versions. Which repository to choose depends on specific requirements: if only stable PHP 5.6 is needed, Webtatic is a good choice; if more version options are required, consider the Remi repository.

Regardless of which third-party repository is chosen, pay attention to its maintenance status and community support. Thorough verification in a test environment before production deployment is recommended.

Best Practice Recommendations

When performing PHP upgrades, follow these best practices: first, verify the upgrade process in a test environment; second, backup important configuration files and databases; third, schedule operations during business off-peak hours; finally, conduct comprehensive testing after upgrade to ensure all functions work properly.

For older systems like CentOS 6, the long-term solution should involve planning system upgrades to newer versions for better security and performance support.