Skip to main content

php -v returns the following message “ea-php82” is not an EA4 SCL PHP

Comments

9 comments

  • cPRex Jurassic Moderator

    Hey there!  This is likely an issue with CageFS on the machine.  Can you try rebuilding CageFS and see if that takes care of the problem? This command will perform that process for you

    cagefsctl --force-update
    0
  • audrey

    Thanks for your help

    I ran ]# cagefsctl --force-update
    and the server says
    -bash: cagefsctl: command not found

    Thanks for also letting me know that this is probably related to the other post that I submitted. I put it as 2 separate posts because I thought it was 2 different issues
    Take Care
    Audrey

     

     

    0
  • audrey
    AlmaLinux v9.8.0 STANDARD kvm
    cPanel Version 1.38.0.18
    0
  • cPRex Jurassic Moderator

    Thanks for confirming the entire system isn't using CloudLinux.  You must be using Imunify on the machine and I saw the CloudLinux extension on those files.

    I can think of two options that would cause this behavior.  The first, is to check and see if any domains are using 8.2 on the machine, with this command:

       whmapi1 php_get_vhost_versions | grep -B2 -A2 ea-php82

    If so, you can reassign it to a different version using the following command:

       whmapi1 php_set_vhost_versions version=ea-php83 vhost-0=example.com

    The second, would be a random leftover configuration file related to the ea-php82 package.  You can check this with the following command:

       grep -rl ea-php82 /etc/cpanel/ea4/ /var/cpanel/userdata/ 2>/dev/null

    Let me know what that says and we can go from there.

    0
  • audrey

    There is only one site on this server. There have never been any other sites on this server. Command does not show any sites on 8.2

    [root@host8 ~]# whmapi1 php_get_vhost_versions | grep -B2 -A2 ea-php82
    [root@host8 ~]# grep -rl ea-php82 /etc/cpanel/ea4/ /var/cpanel/userdata/ 2>/dev/null
    /etc/cpanel/ea4/profiles/pkg-manifest.json
    /etc/cpanel/ea4/ea4-metainfo.json
    /etc/cpanel/ea4/php.conf
    /etc/cpanel/ea4/php.conf.cache
    /etc/cpanel/ea4/php.conf.bak/1790334187.433386
    /etc/cpanel/ea4/php.conf.bak/1790939172.475138
    /etc/cpanel/ea4/php.conf.bak/1790939174.475138
    /etc/cpanel/ea4/php.conf.bak/1790939178.475586
    /etc/cpanel/ea4/php.conf.bak/1790939179.475586
    /etc/cpanel/ea4/php.conf.bak/1791025284.480315
    /etc/cpanel/ea4/php.conf.bak/1791025286.480315
    /etc/cpanel/ea4/php.conf.bak/1791025287.480315
    /etc/cpanel/ea4/php.conf.bak/1791025287.480331
    /etc/cpanel/ea4/php.conf.bak/1791025288.480331
    /etc/cpanel/ea4/php.conf.bak/1791401224.150173
    /etc/cpanel/ea4/php.conf.bak/1791401226.150173
    /etc/cpanel/ea4/php.conf.bak/1791543925.745073
    /etc/cpanel/ea4/php.conf.bak/1791543931.745073
    /etc/cpanel/ea4/php.conf.bak/1792062280.480709
    /etc/cpanel/ea4/php.conf.bak/1792062283.480709
    /etc/cpanel/ea4/php.conf.bak/1792062289.480766
    /etc/cpanel/ea4/php.conf.bak/1792062290.480766
    /etc/cpanel/ea4/php.conf.bak/1792062291.480766
    /etc/cpanel/ea4/php.conf.bak/1792584162.498738
    [root@host8 ~]#

    0
  • cPRex Jurassic Moderator

    Thanks for sharing those details.  It would likely be best to create a ticket for this issue so additional troubleshooting can be performed as that error doesn't make sense with only one site on the machine.

     

    0
  • audrey

    Just remembered that I did set up another test site on this server when I first set up the server. I deleted the test site sometime in July, 2026
    Does this help make sense of the error?

    As far as sending in a ticket - I am unable to send in a ticket because I get this server's cpanel license through the datacenter and I do not have access to send in a ticket.

    Aside from php -v not working and the migrate_local_ini_to_php_ini error, do you see this as a big problem on this server?

     

    0
  • cPRex Jurassic Moderator

    You always have the option to speak with your datacenter and submit a ticket there.  Your license provider has to offer some level of support, and if they can't resolve the issue then they would escalate it to us.

    I still think it's something that should get fixed, but it's not a showstopping bug.

    0
  • audrey

    Thanks for your help!

    I will get in touch with the datecenter.

    I am glad that it is not a show stopping bug.

    Take Care
    Audrey

    0

Please sign in to leave a comment.