Articles in this section

System update fails on a Plesk server with AlmaLinux/CloudLinux: package plesk-php74-imagick requires libMagickCore, but none of the providers can be installed

kb: bug kb: fixed Plesk for Linux

Applicable to:

  • Plesk for Linux

Symptoms

The following errors are being displayed after executing the dnf upgrade or yum update with epel enabled on AlmaLinux or CloudLinux:

CONFIG_TEXT: Error: Problem: package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed
- package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickWand-6.Q16.so.6()(64bit), but none of the providers can be installed
- cannot install both ImageMagick-libs-6.9.12.48-2.el8.x86_64 and ImageMagick-libs-6.9.10.86-1.el8.x86_64
- cannot install both ImageMagick-libs-6.9.10.86-1.el8.x86_64 and ImageMagick-libs-6.9.12.48-2.el8.x86_64
- cannot install the best update candidate for package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64
- cannot install the best update candidate for package ImageMagick-libs-6.9.10.86-1.el8.x86_64
(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)

Cause

Product issue:

  • #PPPM-13570 "On Plesk servers running on Red Hat Enterprise Linux 8 and its derivatives with the Extra Packages for Enterprise Linux (EPEL) repository configured, running the dnf update command now properly updates the “plesk-phpXX-imagick” packages."
    Fixed in:

Resolution

Please consider updating your server:

Workaround

If update is not possible for some reason you may try the following

workaround

If the issue is not fixed automatically, execute the following procedure:

1. Connect to the server via SSH

2. Clean dnf cache:

# dnf clean metadata

3. Re-run system update:

# dnf update

Note: If exclude=ImageMagick-libs line was previously added to/etc/yum.repos.d/epel.repo file as a temporary workaround, remove it.

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.