TL;DR
If your CloudLinux server throws a dependency error like:
Package ea-apache24-mod_lsapi-1:1.1-81.el8.cloudlinux.x86_64 is already installed.
Error:
Problem: cannot install the best candidate for the job
– nothing provides liblsapi >= 1:1.1-85 needed by ea-apache24-mod_lsapi-1:1.1-85.el8.cloudlinux.x86_64 from cl-ea4
(try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)
Fix it by updating the package while explicitly enabling CloudLinux repos:
yum update ea-apache24-mod_lsapi –enablerepo=cloudlinux*
# (On EL8/EL9, `yum` is an alias to `dnf`, so this works either way.)
This pulls the newer liblsapi from the correct repo and completes the upgrade cleanly.
What’s Going On?
- You already have
ea-apache24-mod_lsapiinstalled (e.g.,1:1.1-81). - The system tries to update it to a newer build (e.g.,
1:1.1-85) from the cl-ea4 (CloudLinux EA4) repository. - The newer build requires
liblsapi >= 1:1.1-85, but your package manager can’t see a matchingliblsapibecause the appropriate CloudLinux repositories are disabled/filtered at update time (or cache is stale).
In short: the dependency exists, but your repos aren’t open to fetch it.
Quick Fix (One-Liner)
Run the update while enabling all CloudLinux repos so the matching liblsapi can be resolved:
yum update ea-apache24-mod_lsapi –enablerepo=cloudlinux*
On some systems you may prefer the explicit dnf form:
dnf update ea-apache24-mod_lsapi –enablerepo=cloudlinux*
Why this works: The wildcard
cloudlinux*temporarily enables CloudLinux-provided repos (includingcl-ea4) so your package manager can see and fetch the requiredliblsapiversion.