There could be multiple reasons or cPanel/WHM Update stuck problem. Today we will discuss some of the general problems that user might encounter while updating cPanel.

We will list some of the general problems with their solutions that people face when they try to update cPanel/WHM.

Make sure that your server has at least 3GB Disk Space free before updating cPanel/WHM

Requirements

  • WHM Login Credentials
  • Root Login for Server where cPanel is installed

Update Logs Location – /var/cpanel/updatelogs

Problem #1

panic: corrupt saved stack index

This error might pop up when you try to update cPanel over SSH command and your logs are spammed with above line. This could occur because of corrupt RPM packages on your machine. To fix this run the following command in SSH

/usr/local/cpanel/scripts/check_cpanel_rpms --fix /scripts/autorepair fix_duplicate_cpanel_rpms

Problem #2

23% complete
E Running `/usr/local/cpanel/scripts/updatenow –upcp –log=/var/cpanel/updatelogs/update.1434534492.log –force` failed, exited with code 1 (signal = 0)

This error might occur when you don’t have enough disk space available for update to proceed. Check Disk Space using the command.df -h Free Disk Space should be above 3GB for cPanel upgrade. Free some space followed by the following command

/usr/local/cpanel/scripts/check_cpanel_rpms --fix /scripts/autorepair fix_duplicate_cpanel_rpms

Problem #3

W [FATAL] – There are active transfers to this server. Updates will be blocked until those transfers complete or are aborted.
=> Log closed

This problem arises when there any Account transfers are running in the background. If you’re not actively transferring something you may want to check WHM>>Transfers>Review Transfers and Restores to abort a failed or stalled transfer that may be present.

Problem #4

see http://go.cpanel.net/rpmcheckfailed for more information
The Administrator will be notified to review this output when this script completes
=> Log closed
7% complete
=> Log closed
16% complete
=> Log closed
.
.
.
39% complete    <<<<<<<< STUCK here from couple of minutes

Sometimes update process is stuck at some location and is not proceeding from a couple of minutes which might turn into hours. In this case, you need to check update is running on which process, if you can find the hanging process using the “ps” command.
Example –

ps aux|grep rpm

If so, kill the hanging process with the “kill -9 PID” command, and then rebuild the RPM database:

mkdir /root/old_rpm_dbs/
mv /var/lib/rpm/__db* /root/old_rpm_dbs/
rpm --rebuilddb

Once you do that, try running the following command again:
/usr/local/cpanel/scripts/check_cpanel_rpms --fix /scripts/autorepair fix_duplicate_cpanel_rpms

 

Problem #5

TIMEOUT: RPM DB is not responding after 10 minutes.

This issue arises when your RPM Databases is not responding for the update process. This is to be fixed by rebuilding the RPM Database.

mkdir /root/old_rpm_dbs/
mv /var/lib/rpm/__db* /root/old_rpm_dbs/
rpm --rebuilddb

Once you do that, try running the following command again:
/usr/local/cpanel/scripts/check_cpanel_rpms --fix /scripts/autorepair fix_duplicate_cpanel_rpms

 

If you are facing some other problem while updating WHM and update process is stuck then kindly contact us by opening a ticket with the details. We will help you in every possible way.

Leave a Comment

Your email address will not be published. Required fields are marked *