Issue
On an attempt to run dnf update
or yum update
on CloudLinux you are getting an error with text like the following:
# yum update
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 0:15:08 ago on Fri 09 Sep 2022 08:12:09 PM CEST.
Error:
Problem 1: package kernel-1:4.18.0-372.19.1.lve.el8.x86_64 requires kernel-modules-uname-r = 4.18.0-372.19.1.lve.el8.x86_64, but none of the providers can be installed
- cannot install the best update candidate for package kernel-1:4.18.0-193.28.1.lve1.el8.x86_64
- package kernel-modules-1:4.18.0-372.19.1.lve.el8.x86_64 is filtered out by exclude filtering
or:
# yum update
Problem 1: cannot install the best update candidate for package ea-apache24-mod_lsapi-1:1.1-55.el8.cloudlinux.x86_64
- nothing provides liblsapi = 1:1.1-56.el8.cloudlinux needed by ea-apache24-mod_lsapi-1:1.1-56.el8.cloudlinux.x86_64
- cannot install the best update candidate for package grub2-common-1:2.02-90.el8_3.1.noarch
- problem with installed package grub2-efi-aa64-modules-1:2.02-90.el8_3.1.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
or:
# yum update
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 0:12:40 ago on Sun 27 Aug 2023 02:35:21 AM +08.
Error:
Problem 1: package accelerate-wp-1.3-4.el8.cloudlinux.x86_64 conflicts with cagefs < 7.5.3-1 provided by cagefs-7.5.1.1-1.el8.cloudlinux.x86_64
- cannot install the best update candidate for package cagefs-7.5.1.1-1.el8.cloudlinux.x86_64
- cannot install the best update candidate for package accelerate-wp-1.1-3.el8.cloudlinux.x86_64
Environment
- CloudLinux
- YUM / DNF
Solution
This error can be caused by different reasons and accordingly can be solved in different ways.
If the error tells you that the package is filtered out by exclude filtering:
- Ensure that the mentioned package is not in the exclude line of the YUM or DNF configuration file:
# cat /etc/yum.conf
.....
exclude=bind-chroot dovecot* exim* filesystem kernel-modules nsd* p0f php* proftpd* pure-ftpd*In the example above, the
kernel-modules
is excluded. - Remove the package from that line.
- Try
yum update
once again.
It is always worth checking that the cloudlinux-release
package on your system is up to date, especially if an error tells you that nothing provides the package:
- Check our changelog to know which release version is actual now for your system: https://changelog.cloudlinux.com/
- Check the version of the package on your system, for example with the command:
# rpm -q cloudlinux-release
- If the version of the package on your system is lower than the actual version, you need to update the package using YUM/DNF:
# yum update cloudlinux-release
- When the
cloudlinux-release
package will be the actual version, clear the YUM/DNF cache and try to update packages or install the package you need:# yum clean all && yum makecache
# yum update
Sometimes the error occurs due to a conflict with a package from a third-party repository. In this case, third-party repositories need to be disabled for updating. For example, a package from the EPEL repository is conflicting and we need to disable the repository:
- You can disable it temporarily by running:
# yum update --disablerepo=epel
- Or disable it permanently:
# yum-config-manager --disablerepo=epel
There is also a workaround to skip the best candidate check which can help in some cases, but we do not recommend using it to resolve conflicts with critical packages such as kernel packages, python packages, glibc, etc:
- Edit your
/etc/yum.conf
file and setbest=False
:
# cat /etc/yum.conf | grep "best="
best=False - Clear the YUM/DNF cache and try to update packages or install the package you need:
# yum clean all && yum makecache
# yum update
Comments
2 comments
become this
--
yum update
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 0:02:24 ago on Sunday, September 18, 2022 AM03:26:38 HKT.
Error:
Problem: cannot install the best update candidate for package alt-php74-imunify-sqlite3-7.4.7-2.el8.x86_64
- nothing provides alt-php-internal-common = 7.4.15-3.el8 needed by alt-php-internal-sqlite3-7.4.15-3.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[root@tgt-tko-m901 ~]# yum install alt-php74-imunify-sqlite3-7.4.7-2.el8.x86_64
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 0:02:43 ago on Sunday, September 18, 2022 AM03:26:38 HKT.
Package alt-php74-imunify-sqlite3-7.4.7-2.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root@tgt-tko-m901 ~]# yum install alt-php-internal-common
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 0:02:53 ago on Sunday, September 18, 2022 AM03:26:38 HKT.
Package alt-php-internal-common-7.4.21-3.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root@tgt-tko-m901 ~]# yum install alt-php74-imunify-sqlite3-7.4.7-2.el8.x86_64
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 0:03:04 ago on Sunday, September 18, 2022 AM03:26:38 HKT.
Package alt-php74-imunify-sqlite3-7.4.7-2.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Hello Scicube,
Could you please check what the version of alt-php-internal-common package you have already installed?
Please sign in to leave a comment.