How to Set or Unset RPM Management in WHM

How to Set or Unset RPM Management in WHM

Overview

If you do not want cPanel & WHM’s rpm.versions system to manage an RPM, you can set that RPM’s target to unmanaged. This document provides steps for how to set RPM targets to unmanaged, and how to return RPM targets to a managed state.

Common unmanaged RPM problems

Warning:

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.
  • 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.

Upgrade MySQL/MariaDB interface errors

If you see the following message in WHM’s MySQL or MariaDB Upgrade interface (Home >> Software >> MySQL/MariaDB Upgrade), the RPM target for the blocked version of MySQL is in the uninstalled state:

Your server's MySQL RPM target is set to "uninstalled". You cannot use the MySQL Upgrade feature while your server is in this state. To allow cPanel & WHM to upgrade MySQL on your server, read the rpm.versions system documentation.

Note:

In cPanel & WHM version 11.46 and earlier, this is WHM’s MySQL Upgrade interface (Home >> Software >> MySQL Upgrade).

To correct this issue, you must return the MySQL RPM target to the managed state, to allow cPanel & WHM to manage the RPM.

To return the MySQL RPM target to the managed state, perform the steps in the Return an RPM target to the managed state section below. When you do this, replace service in the example commands with the appropriate target for the blocked version of MySQL.

Important:

In cPanel & WHM version 11.50 and later, if you set a MySQL target to the unmanaged state, the system will also block 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.

Why is my RPM target set to unmanaged?

In cPanel & WHM version 11.34 and earlier, the update settings for these services were configured in the cPanel Package Updates feature. When cPanel implemented the rpm.versions system in cPanel & WHM version 11.36, these services were converted to the RPM system. If the services’ updates were set to Never Update in the cPanel Package Updates interface in cPanel & WHM version 11.34 or earlier, their targets were automatically set as unmanaged in the rpm.versions system during the upgrade to cPanel & WHM version 11.36. While it was sometimes practical to set service updates to Never in earlier versions of cPanel & WHM, the related problems have been solved in more recent versions.


The cPanel Package Updates feature in cPanel & WHM version 11.34

Warning:

We strongly recommend that you to allow the rpm.versions system to manage all RPM targets.

The RPM targets for the following services may be set to the unmanaged state, even if you did not actively change them:

Service
Associated target
Bandmin bandmin

Warning:

We removed the Bandmin feature from cPanel & WHM version 58. The Bandmin feature only exists in cPanel & WHM version 56 and earlier.

Courier courier

Warning:

We removed the Courier mail server in cPanel & WHM version 54. The Courier mail server only exists for cPanel & WHM version 11.52 and earlier.

Dovecot dovecot
FTP proftpd and pure-ftpd
MySQL MySQL50, MySQL51, MySQL55, or MySQL56
NSD nsd

Set an RPM target to unmanaged

To set an RPM target to the unmanaged state, perform the following steps:

  1. Run the following command, where service is the name of the RPM target that you wish to set to the unmanaged state:
    /usr/local/cpanel/scripts/update_local_rpm_versions --edit target_settings.service unmanaged
  2. To confirm that the target is now set to unmanaged, run the following command:
    cat /var/cpanel/rpm.versions.d/local.versions

    You will see unmanaged next to the target name.

Example

If you set the pure-ftpd target to unmanaged, the /var/cpanel/rpm.versions.d/local.versions file might appear similar to the following example:

file_format: 
 version: 2
install_targets: {}
 
rpm_groups: {}
 
rpm_locations: {}
 
srpm_sub_packages: {}
 
srpm_versions: {}
 
target_settings: 
 cpanel-devel: installed
 pure-ftpd: unmanaged
url_templates: {}

Note:

To set FTP services to unmanaged, you must run these commands for both the pure-ftpd and proftpd RPM targets.

Return an RPM target to the managed state

To return an unmanaged RPM target to the managed state, perform the following steps:

  1. Run the following command, where service represents the name of the RPM target that you wish to set to the managed state:
    /usr/local/cpanel/scripts/update_local_rpm_versions --del target_settings.service

    Note:

    When you use the --del option with the /usr/local/cpanel/scripts/update_local_rpm_versions script, you return that RPM target to its default in the managed state, which could be installed oruninstalled.

  2. To confirm that the RPM target is no longer set to unmanaged, run the following command:
    cat /var/cpanel/rpm.versions.d/local.versions

    The /var/cpanel/rpm.versions.d/local.versions file will no longer list that RPM target.

Note:

To return FTP services to the managed state, you may need to run these commands for both the pure-ftpd and proftpd targets.

Was this article helpful?

Related Articles

Leave A Comment?