(Home >> Server Configuration >> Update Preferences)
This interface allows you to define how your server performs software updates and upgrades.
This section of the interface allows you to select a release tier. The release tier that you select controls when the system performs an upgrade to a new major version of cPanel & WHM.
Additionally, this interface allows you to specify how your server performs an update within a major version.
If you perform an update that includes multiple major versions of cPanel & WHM, the update process upgrades your server to each intermediate version. The update process performs compatibility checks for each version prior to the upgrade to that version. If the process encounters blockers, it finishes on the most recent release of cPanel & WHM that is compatible with your system.
For more information, read our Upgrade Blockers documentation.
Select a cPanel & WHM tier that matches your requirements. For more information, read ourdocumentation.
After you upgrade to a new major version of cPanel & WHM, you cannot downgrade to a previous major version of cPanel & WHM.
The following table describes each of the cPanel & WHM release tiers:
Long-Term Support (LTS). If you do not wish to upgrade cPanel & WHM, you can select a cPanel & WHM version for as long as cPanel supports it.
The following table lists the LTS dates for the current versions of cPanel & WHM:
|STABLE||This version has received considerable public exposure, testing, and verification.||Published least frequently.|
This version is feature-complete and we test it thoroughly. It contains all intended features and functionality. New installations default to RELEASE.
|Published more frequently than STABLE.|
|CURRENT||We tested and verify this version, but it may not contain all of the proposed functionality of a release. This tier is similar to the "release candidate" tier that other publication schemes use.||Published more frequently than RELEASE.|
We only perform rudimentary testing on this version. The features are subject to further modification. This version usually lacks official public documentation.
|Published most frequently (up to several times per week).|
To reduce support ticket influx, automatic upgrades to subsequent major versions of cPanel & WHM do not always occur immediately. In certain scenarios, the system applies a zero-to-four-business-day delay before your automatic upgrade executes.
The system applies a delay if all of the following statements are true:
The system randomly selects the length of your delay. For example, if the system detects a new major version on a Friday, the upgrade does not take place until the following Monday, Tuesday, Wednesday, or Thursday.
When we release a major version, you may perform any of the following actions:
Before an upgrade, ensure that the new version is compatible with any third-party software or customizations to your system. We recommend that you stage the upgrade on a test system before you upgrade your production system.
Use this menu to select how you want cPanel & WHM to update. You can choose from the following options:
/usr/local/cpanel/scripts/upcpscript as the
The maintenance portion of the
The upgrade to newer versions of cPanel & WHM requires a minimum amount of disk space in order to stage the files necessary. This feature determines where the system places the staging files.
If the selected directory does not have enough disk space for the update, the system automatically selects a different directory for the next attempt. An email will notify you of the new selection, and you will have 24 hours to change the new directory.
To select the staging directory for the updates, perform one of the following actions:
.cpanel__HOSTNAME__upcp_stagingsubdirectory at that location, where
hostnameis the name of the actual server.
Select a partition. The path to the selected partition will appear in the Directory text box. The Available Partitions table displays the available disk space on each of your partitions.
This feature determines whether the nightly maintenance tasks will update the RPM packages from your operating system distribution. This is similar to the
/usr/local/cpanel/scripts/upcpscript to update operating system packages.
/usr/local/cpanel/scripts/upcpscript runs. If you select this option, you must run the
/usr/local/cpanel/scripts/rpmup2script to update your operating system packages.
This setting does not effect cPanel-provided RPMs.
This feature defines how you wish to update the Apache SpamAssassin rules.
/usr/local/cpanel/scripts/upcpscript to update Apache SpamAssassin rules.
Select the Send my settings to all configuration cluster servers checkbox to send your Update Preferences settings to all of the servers that are currently in your configuration cluster.
The interface only displays the Send my settings to all configuration cluster servers checkbox if you have already added additional servers to the configuration cluster with the Configuration Cluster interface (Home >> Clusters >> Configuration Cluster).
If you selected this option, the interface may require several seconds to load when you click Save, and will then display a confirmation message: