error after upgrade
Hi,
Server is still Centos 7.9.
On April 30th cPanel automatically upgrade it from 11.110.0.50 -> 11.110.0.97 and since then it is a problem with PHP.
The first error in the upgrade log is:
/opt/cpanel/ea-php74/root/usr/sbin/php-fpm: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php74/root/usr/sbin/php-fpm)
But the migration script also didn't work:
E [/usr/local/cpanel/scripts/migrate_local_ini_to_php_ini] /opt/cpanel/ea-php52/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php52/root/usr/bin/php)
In the meantime the automatically upgrade process continued:
[2026-05-05 01:57:25 +0300] Completed update 11.110.0.97 -> 11.110.0.112
[2026-05-09 01:57:24 +0300] Completed update 11.110.0.112 -> 11.110.0.117
[2026-05-14 01:57:21 +0300] Completed update 11.110.0.117 -> 11.110.0.119
[2026-05-21 01:57:19 +0300] Completed update 11.110.0.119 -> 11.110.0.121
Now I'm on 11.110.0.121 and the email server is working (fortunately it is the only part we are using).
The /usr/local/cpanel/scripts/migrate_local_ini_to_php_ini continue to exist with error regarding php53.
The default PHP version is ea-php72 and I cannot change it because I have only errors in the web interface.
Any recommendations are appreciated.
Thanks
-
Hey there! The recent updates were related to security and I wouldn't expect things to change regarding PHP with these older versions.
Are you seeing anything that actually isn't working on the machine, or are you just seeing these warnings in the logs? If these are just log entries you can ignore those.
Can you let me know the specific error you're seeing in the interface regarding the PHP version change issue? I would also expect there to be more details around that in the main cPanel log at /usr/local/cpanel/logs/error_log.
0 -
Hi,
As soo as I go to Software->MultiPHP Manager i see the error:
Error: (XID umjjgk) 10 errors occurred: Error #1: The “ea-php53” package does not expose a version number. Error #2: The “ea-php54” package does not expose a version number. Error #3: The “ea-php55” package does not expose a version number. Error #4: The “ea-php56” package does not expose a version number. Error #5: The “ea-php70” package does not expose a version number. Error #6: The “ea-php71” package does not expose a version number. Error #7: The “ea-php72” package does not expose a version number. Error #8: The “ea-php73” package does not expose a version number. Error #9: The “ea-php74” package does not expose a version number. Error #10: The “ea-php80” package does not expose a version number.
If I try to change the php version I see this error:
Error: API failure: (XID 3x5uby) The “ea-php72” package does not expose a version number.
In the /usr/local/cpanel/logs/error_log I can see these entries:
[2026-05-28 08:06:23 +0300] info [xml-api] (XID umjjgk) 10 errors occurred:
Error #1: The “ea-php53” package does not expose a version number.
Error #2: The “ea-php54” package does not expose a version number.
Error #3: The “ea-php55” package does not expose a version number.
Error #4: The “ea-php56” package does not expose a version number.
Error #5: The “ea-php70” package does not expose a version number.
Error #6: The “ea-php71” package does not expose a version number.
Error #7: The “ea-php72” package does not expose a version number.
Error #8: The “ea-php73” package does not expose a version number.
Error #9: The “ea-php74” package does not expose a version number.
Error #10: The “ea-php80” package does not expose a version number. [php_get_handlers] version [1].
/opt/cpanel/ea-php72/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php72/root/usr/bin/php)
/opt/cpanel/ea-php72/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php72/root/usr/bin/php)
/opt/cpanel/ea-php72/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php72/root/usr/bin/php)
/opt/cpanel/ea-php72/root/usr/bin/php: /opt/cpanel/ea-libxml2/lib64/libxml2.so.2: no version information available (required by /opt/cpanel/ea-php72/root/usr/bin/php)
/opt/cpanel/ea-php72/root/usr/bin/php: symbol lookup error: /opt/cpanel/ea-php72/root/usr/bin/php: undefined symbol: __xmlParserVersion
[2026-05-28 08:07:20 +0300] info [xml-api] API failure: (XID 3x5uby) The “ea-php72” package does not expose a version number. [php_set_system_default_version] version [1].0 -
Thanks for the additional details - that's exactly what I needed to see.
Can you try reinstalling the php-cli packages for each PHP version on your machine? For example,
yum install ea-php74-php-cli
and see if that changes the behavior?
0 -
Unfortunately I can't reinstall it:
yum install ea-php74-php-cli
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 184.94.200.2
* cpanel-addons-production-feed: 184.94.200.2
* cpanel-plugins: 184.94.200.2
* epel: ftp-stud.hs-esslingen.de
Package matching ea-php74-php-cli-7.4.33-18.24.6.cpanel.x86_64 already installed. Checking for update.
Nothing to doAnd nothing is changed.
0 -
Since it's already showing as installed, do a "yum reinstall ea-php74-php-cli". That should download and install it over top of the existing install, and should replace any missing/broken files/links.
1 -
Thanks mtindor.
Unfortunately I still don't have much luck:
yum reinstall ea-php74-php-cli
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 3.9 kB 00:00:00
* EA4: 184.94.200.2
* cpanel-addons-production-feed: 184.94.200.2
* cpanel-plugins: 184.94.200.2
* epel: ftp-stud.hs-esslingen.de
Installed package 1:ea-php74-php-cli-7.4.33-1.el7.cloudlinux.x86_64 (from imunify360-ea-php-hardened) not available.
Error: Nothing to do0 -
That's a clue - it looks like at one point your server had Imunify installed, but maybe that is no longer the case?
It might be easier to help with this issue through a ticket as this is something that should be a quick fix when working directly on the server.
0
Please sign in to leave a comment.
Comments
7 comments