Preguntes Freqüents - FAQ

Overview

The Warden extension requires ClamAV packages from the EPEL repository. If a conflicting third-party repository, such as Imunify360, is installed without an exclusion rule for ClamAV packages, the installer will fail due to package conflicts. This article provides instructions on how to resolve this error by configuring the appropriate repository exclusions.

Prerequisites

• Root or sudo access to the server
• A command-line text editor (e.g., vi, nano)

Resolution Steps

1. Identify the correct repository configuration file based on your server environment:
   • Standard installations: /etc/yum.repos.d/imunify360.repo
   • CloudLinux servers: /etc/yum.repos.d/cloudlinux-imunify360.repo
2. Open the identified file using a text editor.
3. Locate the [imunify360] section within the configuration file.
4. Append the following line to the end of this section: exclude=clam*
5. Save and close the file.
6. Re-run the Warden extension installer. The installation process should now complete successfully.

Configuration Example

The following examples demonstrate the repository configuration before and after applying the required exclusion rule.

Before:

[imunify360]
name=EL-7 - Imunify360
baseurl=https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/
username=defense360
password=nraW!F@$x4Xd6HHQ
enabled=1
gpgcheck=1
gpgkey=https://repo.imunify360.cloudlinux.com/defense360//RPM-GPG-KEY-CloudLinux

After:

[imunify360]
name=EL-7 - Imunify360
baseurl=https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/
username=defense360
password=nraW!F@$x4Xd6HHQ
enabled=1
gpgcheck=1
gpgkey=https://repo.imunify360.cloudlinux.com/defense360//RPM-GPG-KEY-CloudLinux
exclude=clam*

Troubleshooting

• If the installer continues to fail, verify that the exclude=clam* directive was added directly under the [imunify360] section and not within a different repository block.
• Ensure there are no trailing spaces or syntax errors in the .repo file, as malformed configuration files can cause YUM to reject the changes.
• If package metadata conflicts persist, clear the local cache by running yum clean all before retrying the installation.