Fix CL 8 YUM Update Errors Related to EA-LSAPI, EA Profiles

1. Issue Description

When running yum update -y on a CloudLinux 8 server with cPanel/WHM, the update may fail with dependency and package conflict errors.

Reported Error

Problem 1: cannot install the best update candidate for package ea-apache24-mod_lsapi-1:1.1-86.el8.cloudlinux.x86_64
 - nothing provides criu-lve >= 4.2-4 needed by ea-apache24-mod_lsapi-1:1.1-96.el8.cloudlinux.x86_64 from cl-ea4
 - nothing provides liblsapi >= 1:1.1-96 needed by ea-apache24-mod_lsapi-1:1.1-96.el8.cloudlinux.x86_64 from cl-ea4

Problem 2: cannot install both ea-profiles-cpanel-4:1.0-53.el8.cloudlinux.1.x86_64 from cloudlinux-x86_64-server-8 and ea-profiles-cpanel-5:1.0-73.79.1.cpanel.x86_64 from @System
 - cannot install the best update candidate for package ea-profiles-cpanel-5:1.0-73.79.1.cpanel.x86_64
 - cannot install the best update candidate for package ea-profiles-cloudlinux-4:1.0-75.el8.cloudlinux.1.x86_64

Running yum update -y --skip-broken may produce the same errors.

2. Possible Causes

  • ea-apache24-mod_lsapi is excluded from updates in /etc/yum.conf.

  • Required dependencies, such as criu-lve and liblsapi, are unavailable from the enabled repositories.

  • CloudLinux and cPanel EasyApache profile packages have conflicting versions.

  • YUM/DNF repository metadata is outdated or repository configuration needs attention.

3. Resolution Procedure

Step 1: Edit /etc/yum.conf

Open the configuration file:

nano /etc/yum.conf

Find the exclude directive. For example:

exclude=ea-apache24-mod_lsapi kernel*

Remove only ea-apache24-mod_lsapi, keeping all other excluded packages.

The corrected line should look like this:

exclude=kernel*

If no other excluded packages remain, remove the entire exclude line.

Save and exit:

  1. Press Ctrl + O.

  2. Press Enter.

  3. Press Ctrl + X.

Verify the configuration:

grep -nEi '^[[:space:]]*exclude[[:space:]]*=' /etc/yum.conf

If ea-apache24-mod_lsapi was not listed, leave the file unchanged and proceed.

Step 2: Clean and Refresh Repository Metadata

Run:

dnf clean all
dnf makecache

Update the CloudLinux release package:

dnf update cloudlinux-release -y

If this command fails, resolve the reported repository or dependency issue before continuing.

Step 3: Verify Enabled Repositories

Check the CloudLinux and EasyApache repositories:

dnf repolist --all | grep -Ei 'cloudlinux|cl-ea4|ea4'

Confirm that the repositories required for CloudLinux and EasyApache packages are available and appropriately enabled.

Step 4: Check Required Dependencies

Run:

dnf repoquery --available --qf '%{name} %{evr} %{repoid}' criu-lve liblsapi

The required versions from the reported error are:

  • criu-lve >= 4.2-4

  • liblsapi >= 1:1.1-96

If compatible versions are unavailable, investigate repository access, configuration, and package availability before retrying the update.

Step 5: Check Installed Package Versions

Run:

rpm -q cloudlinux-release ea-apache24-mod_lsapi ea-profiles-cpanel ea-profiles-cloudlinux

Check enabled repositories:

dnf repolist --enabled

If the ea-profiles-cpanel conflict remains, verify the correct package versions and repository configuration before attempting to replace or remove packages.

Do not force-remove packages or use --allowerasing without reviewing the transaction.

Step 6: Update the EA-LSAPI Package

Once the repository configuration and required dependencies have been verified, run:

dnf update ea-apache24-mod_lsapi --enablerepo='cl*'

Review the proposed transaction and confirm it only if the package changes are appropriate.

If the command succeeds, continue to the full system update.

Step 7: Run the Full System Update

Execute:

yum update -y

If the system still reports the same errors, do not repeatedly retry with --skip-broken. Review the dependency and package conflict details first.

Step 8: Verify the Result

Check the installed package versions:

rpm -q ea-apache24-mod_lsapi ea-profiles-cpanel ea-profiles-cloudlinux

Check for dependency problems:

dnf check

Preview any remaining updates without approving the transaction:

dnf update --assumeno

If no blocking dependency or package conflict remains, the update issue is resolved.

4. Important Notes

  • Back up important configuration files and take a suitable server snapshot before package-level changes.

  • Removing the LSAPI package from the exclude list only allows it to be considered for updates; it does not fix missing dependencies or conflicting package versions by itself.

  • Do not use rpm -e --nodeps or force package replacement to bypass the conflict.

  • If the error persists, collect the outputs from the repository and package checks and escalate to CloudLinux or cPanel support.

5. Summary of Update Commands

After completing the configuration and dependency checks, the main update sequence is:

dnf clean all
dnf makecache
dnf update cloudlinux-release -y
dnf update ea-apache24-mod_lsapi --enablerepo='cl*'
yum update -y
dnf check

Run the commands in sequence, reviewing any errors before proceeding to the next step.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Domain names are not showing in WHM

We were unable to see any domains listed under WHM -> List Accounts. However, we can see the...

How to Start/Stop or Restart Apache server

Apache is the HTTP server that is freely available over the internet. It is a kind of software or...

How to install Attracta SEO Tools plugin

RequirementscPanel/WHM needs to be installed on your server. Step 1: SSH into your server and go...

How to Install CpCleaner in cPanel through SSH?

Installation Run the following shell commands as root via SSH: wget -O cpc-1.0.3.tar...

How to Secure a cPanel/WHM Web Server

Here are a few basic steps that you should keep in mind for keeping a server secure. 1) Strong...