cPanel & WHM update failure in upcp script - v84.0.21 to 86.0.4
Since Feb 6, 2020 cPanel has been failing to update.
WHM does not seem to understand the server name. It used to read server1.DomainName
The actual server OS is below
I get this message in the email notification
Starting yesterday I get the not only the message above but I also get this one. It seems like it is trying to run the update twice.
I tried once last week to do the update manually without the force. I looks like a database is corrupt. How do I run the database recovery and should that be the next step I take to resolve this issue? Note I have root access
/etc/redhat-release:CentOS release 6.10 (Final)
/usr/local/cpanel/version:11.84.0.21
/var/cpanel/envtype:standard
CPANEL=release
root@server1 [~]# I get this message in the email notification
[2020-02-20 04:42:18 -0500] Running version '11.84.0.21' of updatenow.
[2020-02-20 04:42:20 -0500] Retrieved public key from vendor: cpanel, category: development, url: https://securedownloads.cpanel.net/cPanelDevelopmentKey.asc
[2020-02-20 04:42:20 -0500] Retrieved public key from vendor: cpanel, category: release, url: https://securedownloads.cpanel.net/cPanelPublicKey.asc
[2020-02-20 04:42:20 -0500] Detected version '11.84.0.21' from version file.
[2020-02-20 04:42:34 -0500] Target version set to '11.86.0.4'
[2020-02-20 04:42:34 -0500] Switching to version 11.86.0.4 of updatenow to determine if we can reach that version without failure.
[2020-02-20 04:42:36 -0500] ***** FATAL: Failed to download updatenow.static from server: (XID cpa8x2) "/bin/rpm" reported error code "1" when it ended: rpmdb: Thread/process 24124/47942435202208 failed: Thread died in Berkeley DB library
[2020-02-20 04:42:36 -0500] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2020-02-20 04:42:36 -0500] error: cannot open Packages index using db3 - (-30974)
[2020-02-20 04:42:36 -0500] error: cannot open Packages database in /var/lib/rpm
[2020-02-20 04:42:36 -0500] rpmdb: Thread/process 24124/47942435202208 failed: Thread died in Berkeley DB library
[2020-02-20 04:42:36 -0500] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2020-02-20 04:42:36 -0500] error: cannot open Packages database in /var/lib/rpm
[2020-02-20 04:42:36 -0500] rpmdb: Thread/process 24124/47942435202208 failed: Thread died in Berkeley DB library
[2020-02-20 04:42:36 -0500] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2020-02-20 04:42:36 -0500] error: cannot open Packages database in /var/lib/rpm
[2020-02-20 04:42:36 -0500] The Administrator will be notified to review this output when this script completes
=> Log closed Thu Feb 20 04:42:36 2020
[2020-02-20 04:42:36 -0500] 17% complete
=> Log closed Thu Feb 20 04:42:36 2020
----------------------------------------------------------------------------------------------------
=> Log opened from /usr/local/cpanel/scripts/maintenance (19471) at Thu Feb 20 04:42:38 2020
=> Log closed Thu Feb 20 04:42:39 2020
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (19350) at Thu Feb 20 04:42:39 2020
Starting yesterday I get the not only the message above but I also get this one. It seems like it is trying to run the update twice.
=> Log opened from /usr/local/cpanel/scripts/updatenow (19352) at Thu Feb 20 04:42:18 2020
[2020-02-20 04:42:18 -0500] Running version '11.84.0.21' of updatenow.
[2020-02-20 04:42:20 -0500] Retrieved public key from vendor: cpanel, category: development, url: https://securedownloads.cpanel.net/cPanelDevelopmentKey.asc
[2020-02-20 04:42:20 -0500] Retrieved public key from vendor: cpanel, category: release, url: https://securedownloads.cpanel.net/cPanelPublicKey.asc
[2020-02-20 04:42:20 -0500] Detected version '11.84.0.21' from version file.
[2020-02-20 04:42:34 -0500] Target version set to '11.86.0.4'
[2020-02-20 04:42:34 -0500] Switching to version 11.86.0.4 of updatenow to determine if we can reach that version without failure.
[2020-02-20 04:42:36 -0500] ***** FATAL: Failed to download updatenow.static from server: (XID cpa8x2) "/bin/rpm" reported error code "1" when it ended: rpmdb: Thread/process 24124/47942435202208 failed: Thread died in Berkeley DB library
[2020-02-20 04:42:36 -0500] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2020-02-20 04:42:36 -0500] error: cannot open Packages index using db3 - (-30974)
[2020-02-20 04:42:36 -0500] error: cannot open Packages database in /var/lib/rpm
[2020-02-20 04:42:36 -0500] rpmdb: Thread/process 24124/47942435202208 failed: Thread died in Berkeley DB library
[2020-02-20 04:42:36 -0500] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2020-02-20 04:42:36 -0500] error: cannot open Packages database in /var/lib/rpm
[2020-02-20 04:42:36 -0500] rpmdb: Thread/process 24124/47942435202208 failed: Thread died in Berkeley DB library
[2020-02-20 04:42:36 -0500] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2020-02-20 04:42:36 -0500] error: cannot open Packages database in /var/lib/rpm
[2020-02-20 04:42:36 -0500] The Administrator will be notified to review this output when this script completes
=> Log closed Thu Feb 20 04:42:36 2020
I tried once last week to do the update manually without the force. I looks like a database is corrupt. How do I run the database recovery and should that be the next step I take to resolve this issue? Note I have root access
-
from the error messages it looks like you have corruption in the RPM databases. There are lots of resources on rebuilding the RPM database. I'd suggest opening a cPanel ticket and have them double check that's the issue. 0 -
I can actually say without a doubt this is RPM DB Corruption. You can repair this through WHM (or attempt to) by going to WHM>>Software>>Rebuild RPM Database 0 -
I am having the same problem and I am almost sure the reason cPanel has already stop supporting CentOS 6 .. forcing us to move to CentOS 7 !!! If I am wrong, please let me know why i can't go further update and stack on cPanel v86.0.21 ?? 0 -
CentOS 6 is still supported till November and the LTS version remains supported as far as I know. If you have the same issue try rebuild the RPM database as @cPanelLauren mentioned. 0 -
cPanel is not forcing you to update and would not corrupt your RPM database purposely. If you want to remain on CentOS 6 past its EoL date you are welcome to do so but you will not be able to update to v88 of cPanel & WHM as we do not support end of life software including operating systems. You will need to stay on the LTS tier to do so or purchase CloudLinux 6. The LTS tier will have v86 until next year when it is updated. At that time you will not be able to update further without updating your OS. 0
Please sign in to leave a comment.
Comments
5 comments