Page tree
Skip to end of metadata
Go to start of metadata

For cPanel & WHM version 64


An RPM target represents the group of RPMs that must exist on the server for a specific service to function properly.

What is an RPM target?

The rpm.versions system uses the target setting to determine whether to install or uninstall that target's specific RPMs. The target_settings section of the /usr/local/cpanel/etc/rpm.versions file contains the cPanel-provided default status for each target.

For example, the cPanel-provided distribution of ClamAV consists of three RPMs: 

  • cpanel-clamav
  • cpanel-clamav-virusdefs
  • cpanel-perl-522-File-Scan-ClamAV

In the /usr/local/cpanel/etc/rpm.versions file, the setting for the clamav RPM target controls how the rpm.versions system manages all three of these components. 

For more information about the /usr/local/cpanel/etc/rpm.versions file, read our The rpm.versions File documentation.

List of RPM targets

For a complete list of RPM targets, read our How to Set or Unset RPM Management documentation.

RPM target states

The RPM targets on your server may be in any of the following states:

  • installed — The rpm.versions system ensures that the RPMs that are associated with that target are installed and functional.
  • uninstalled — The rpm.versions system ensures that the RPMs that are associated with that target are uninstalled.
  • unmanaged  — The rpm.versions system ignores the RPMs that are associated with that target, regardless of whether they are installed on the server.


    You may experience problems with certain services if their targets are set to unmanaged:
    • The rpm.versions system does not update RPMs for which the target is set to unmanaged. These RPMs require manual upgrades and maintenance.
    • If you upgrade a server for which the FTP targets are set to unmanaged, problems may occur in cPanel's FTP-related interfaces. 
      • For more information, read our RPM Targets documentation.
    • It is possible that unmanaged RPM targets may become upgrade blockers for a future version of cPanel & WHM.
    • If you set a MySQL target to the unmanaged state, the system also blocks MariaDB on the server. To successfully use a cPanel-managed installation of either MySQL or MariaDB, the rpm.versions system must manage both softwares' RPM targets.

For more information, read our RPM Targets documentation.

Legacy RPMs

The RPMs that cPanel provided prior to the implementation of the rpm.versions system are now called "legacy" RPMs. The settings in the /var/cpanel/cpanel.config file control these legacy RPMs. The system stores these settings in the /usr/local/cpanel/etc/rpm.versions file.


As with all RPMs, the files in the /var/cpanel/rpm.versions.d/ directory can override the target_settings configuration. 

cpanel.config file settings

The following table lists the settings in the /var/cpanel/cpanel.config file that control the actions of legacy RPMs:

cpanel.config settingRPM target
mysql-versionMySQL55, MySQL56, MariaDB100
local_nameserver_typebind, mydns, nsd
mailserverdovecot, exim
ftpserverpure-ftpd, proftpd

For more information, read our RPM Targets documentation.

Additional documentation

  • RPM Targets — This document provides steps for how to set RPM targets to unmanaged, and how to return RPM targets to a managed state.
  • RPM Targets — This document explains the files in the /var/cpanel/rpm.versions.d/ directory, which system administrators and third-party developers can use to modify cPanel-provided RPM management.
  • RPM Targets — Use the /scripts/update_local_rpm_versions script to update the /var/cpanel/rpm.versions.d/local.versions file.

There is no content with the specified labels