How To… Manage cPanel Versions

How To...Published January 24, 2012 at 1:57 pm No Comments

 

 

cPanel needs to be updated periodically to ensure that security standards are up to date and also to release new features, ect. When cPanel releases a new version of it’s software, they typically release it in the following 4 tiers:

Tier 1: STABLE

This version has already undergone considerable public exposure, testing, and verification. The STABLE version is publish least frequently.

Tier 2: RELEASE

This version is similar to STABLE, but has received less testing and is released more frequently. New installations default to RELEASE.

Tier 3: CURRENT

This version has been tested and verified, but may not have the same functionality of RELEASE. Also published more frequently than RELEASE.

Tier 4: EDGE

Has only undergone rudimentary testing. Features are subject to further public documentation. This version is published most frequently – usually up to several times per week.

Server administrators should select a Tier that falls in line with their goals and intended usage for that server. For instance, any server used for production purposes should only select the most stable hosting environment (STABLE). It’s imporant to note (as mentioned above) that new cPanel installations will default to RELEASE so you will have to manually change the version to STABLE after the initial installation of cPanel. EDGE server builds should only be used for compatibility and functionality testing in a controlled environment.

To change your versions of cPanel, you will need to edit the cpupdate config file found here:

 

root@server [~]# nano /etc/cpupdate.conf

This will open a text editor with the following contents already listed (or very similar to):

 

BANDMINUP=inherit
COURIERUP=inherit
CPANEL=release
EXIMUP=inherit
FTPUP=inherit
MYSQLUP=inherit
PYTHONUP=inherit
RPMUP=daily
SYSUP=daily

If you wish to change your version from RELEASE to STABLE you will have to change the value for “CPANEL=” from:

 

CPANEL=release

to

 

CPANEL=stable

Save your changes and exit the nano text editor. You will now want to force run a cPanel update so that the server picks up the new changes. Since this can typically take 30 mins to an hour to complete, its best to run this cPanel update in screen:

 

root@server [~]# screen
root@server [~]# /scripts/upcp --force

After the update is complete, you will have a much more stable version of cPanel with much the same functionality it originally came with.

 

Have any questions or comments? If so, let us know by either sounding off below or leaving a comment on our Facebook page or by tweeting us at VPSLatch!