EasyApache 4 Not Updating

[cool_recep]

According to EA4 release notes I should be running on PHP 8.1.16 but I have 8.1.14 and EA says it's up to date. Tried yum clean all, yum makecache and yum update but still the same.

• Alma 8.7
• cPanel 108.0.14

 

[cPRex]

Hey there! My personal machine is also running AlmaLinux 8.7 and I see the .16 versions there.

When you run the "yum update" command do you see any odd output there? If you manually check the RPM version , does that also show .14?

rpm -qa | grep ea-php81-8

 

[cool_recep]

It says ea-php81-8.1.14-1.el8.cloudlinux.x86_64.

yum update:

Last metadata expiration check: 0:12:39 ago on Mon 06 Mar 2023 09:05:10 PM +03.
Dependencies resolved.
Nothing to do.
Complete!

BTW, code button here opens up forum list somehow.

 

[cPRex]

Yes, we know about the code button issue.

Are you sure you are running AlmaLinux as the operating system? That output shows it was installed from a CloudLinux RPM, and those do run just a bit behind while they ge them into their systems, so if you are using CloudLinux things are working as expected.

 

[cool_recep]

I think so: AlmaLinux v8.7.0 STANDARD standard

4.18.0-372.26.1.el8_6.x86_64

NAME="AlmaLinux"
VERSION="8.7 (Stone Smilodon)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.7"
PLATFORM_ID="platform:el8"
PRETTY_NAME="AlmaLinux 8.7 (Stone Smilodon)"
ANSI_COLOR="0;34"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:almalinux:almalinux:8::baseos"
HOME_URL="https://almalinux.org/"
DOCUMENTATION_URL="https://wiki.almalinux.org/"
BUG_REPORT_URL="https://bugs.almalinux.org/"

ALMALINUX_MANTISBT_PROJECT="AlmaLinux-8"
ALMALINUX_MANTISBT_PROJECT_VERSION="8.7"
REDHAT_SUPPORT_PRODUCT="AlmaLinux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.7"

 

[cPRex]

The most likely explanation is that this was converted back to AlmaLinux from CloudLinux, but there are still packages left on the system that were installed by CloudLinux. The issue you're experiencing is still normal as CloudLinux doesn't forcibly remove all the packages from the system when the OS is removed. More details on that can be found in the very bottom text block on this page:

Installation

CloudLinux OS supports all the hardware supported by RHEL/CentOS/AlmaLinux, with few exceptions. Exceptions are usually hardware that require binary drivers, and that doesn't have any open source alternatives.

docs.cloudlinux.com

However, it's possible your server would still have the old repositories present on the system. You can check /etc/yum.repos.d/ to see if there is anything listed from CloudLinux there. Here is what I see on my personal AlmaLinux machine:

-rw-r--r--    1 root root  943 Nov 18 21:44 almalinux-ha.repo
-rw-r--r--    1 root root  905 Nov 18 21:44 almalinux-nfv.repo
-rw-r--r--    1 root root  885 Nov 18 21:44 almalinux-plus.repo
-rw-r--r--.   1 root root  971 May 23  2022 almalinux-powertools.repo
-rw-r--r--    1 root root  963 May 11  2022 almalinux-powertools.repo.rpmnew
-rw-r--r--    1 root root 2.7K Nov 18 21:44 almalinux.repo
-rw-r--r--    1 root root 1.1K Nov 18 21:44 almalinux-resilientstorage.repo
-rw-r--r--    1 root root  871 Nov 18 21:44 almalinux-rt.repo
-rw-r--r--    1 root root  928 Nov 18 21:44 almalinux-saphana.repo
-rw-r--r--    1 root root  873 Nov 18 21:44 almalinux-sap.repo
-rw-r--r--.   1 root root  257 Mar  8  2022 cPAddons.repo
-rw-------    1 root root  241 Mar  6 05:34 cpanel-plugins.repo
-rw-r--r--.   1 root root  204 Jun 22  2021 EA4.repo
-rw-r--r--    1 root root 1.7K Oct  3 19:26 epel-modular.repo
-rw-r--r--    1 root root 1.4K Oct  3 19:26 epel.repo
-rw-r--r--    1 root root 1.8K Oct  3 19:26 epel-testing-modular.repo
-rw-r--r--    1 root root 1.4K Oct  3 19:26 epel-testing.repo
-rw-r--r--    1 root root 1.2K Apr 27  2022 mysql-community-debuginfo.repo
-rw-r--r--    1 root root 1.3K Apr 27  2022 mysql-community.repo
-rw-r--r--    1 root root 1.3K Apr 27  2022 mysql-community-source.repo
-rw-r--r--.   1 root root  304 Feb 21 06:27 wp-toolkit-cpanel.repo

 

[cool_recep]

What is the command to list those?

I get this:

repo id                       repo name
EA4                           EA4 ( EasyApache 4 )
MariaDB106                    MariaDB106
appstream                     AlmaLinux 8 - AppStream
baseos                        AlmaLinux 8 - BaseOS
cpanel-addons-production-feed cPanel Addons Production Feed
cpanel-plugins                cPanel Plugins project
elasticsearch                 Elastic repository for 8.x packages
elrepo                        ELRepo.org Community Enterprise Linux Repository -                                                                                                 el8
epel                          Extra Packages for Enterprise Linux 8 - x86_64
extras                        AlmaLinux 8 - Extras
imunify360                    EL-8 - Imunify360
imunify360-ea-php-hardened    Imunify360 ea-php Hardened repository for CentOS 8                                                                                                 - x86_64
imunify360-rollout-1          Imunify360 - Gradual Rollout Slot 1
imunify360-rollout-2          Imunify360 - Gradual Rollout Slot 2
imunify360-rollout-3          Imunify360 - Gradual Rollout Slot 3
imunify360-rollout-4          Imunify360 - Gradual Rollout Slot 4
kernelcare                    kernelcare
powertools                    AlmaLinux 8 - PowerTools
remi-modular                  Remi's Modular repository for Enterprise Linux 8 -                                                                                                 x86_64
remi-safe                     Safe Remi's RPM repository for Enterprise Linux 8                                                                                                 - x86_64
wp-toolkit-cpanel             WP Toolkit for cPanel
wp-toolkit-thirdparties       WP Toolkit third parties

 

[cPRex]

My output was just the directory listing from the /etc/yum.repos.d directory on the system.

If you're not seeing them from "yum repolist" they have likely been removed.

I still believe my theory about the server having been converted back from CloudLinux is correct. You can see if the system had a license through them directly at https://cln.cloudlinux.com/console/check-license or through us at cPanel & WHM License Verification | cPanel, L.L.C.

 

[cool_recep]

Only Imunify360 Unlimited license shows up. And this is on the cPanel side:

 

[cPRex]

It's possible that hardened PHP versions were installed from Imunify360. At this point it would likely be best to open a ticket so we could check the system directly.

 

[cool_recep]

This problem still persists! I'm on 8.1.16 which is from February!

 

[cPRex]

Did you ever create a ticket on this issue?

 

[cool_recep]

My hosting guy did and the answer was that it was going to be fixed in the next cPanel release, which already came.

 

[cPRex]

Would you happen to have the ticket number? It should start with 94 or 95.

 

[cool_recep]

He could not find it. So I created a new one.

95064482

 

[cPRex]

Thanks for posting that number - I'm following along with that now, although I see we are having difficulty accessing SSH on the system.

 

[cool_recep]

I’ve updated the IP list. If the problem persists, I’ll change the Firewall settings.

 

[cPRex]

Just be sure to let them know in the ticket.

 

[cPRex]

I see we found that you are using the hardened PHP packages from Imunify360, but also that the Imunify360 license is expired. We recommended removing that tool or renewing the license to get this working.