Knowledgebase

Symptoms

On servers that make use of Imunify360 or CloudLinux hardened PHP for the ea-php packages, after updating the EasyApache packages, you find that PHP-FPM fails to start with the following errors:

/opt/cpanel/ea-php##/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available
/opt/cpanel/ea-php##/root/usr/bin/php: symbol lookup error: undefined symbol: __xmlParserVersion
/opt/cpanel/ea-php##/root/usr/sbin/php-fpm: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available
/opt/cpanel/ea-php##/root/usr/sbin/php-fpm: symbol lookup error: undefined symbol: __xmlParse

You may also find that the errors here are reported by cron jobs and in the output of PHP commands:

/opt/cpanel/ea-php##/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php##/root/usr/bin/php)
/opt/cpanel/ea-php##/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php##/root/usr/bin/php)

Cause

This behavior is observed on servers that use Imunify360 / CloudLinux hardened EA PHP packages, caused by the update to the cPanel-provided ea-libxml2 package. The Hardened PHP packages need to be rebuilt to use the new ea-libxml2 package, which will be addressed in an update to the Hardened ea-php packages.

Resolution

The resolution to this issue, currently recommended by CloudLinux, is to downgrade the ea-libxml2 package:

dnf downgrade ea-libxml2

You may want to version lock this package to prevent it from upgrading until the core issue is resolved:

How to version lock RPM packages

Additional Information

CloudLinux: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php83/root/usr/bin/php)