Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SOLVED cPanel update failed

Discussion in 'General Discussion' started by Zabidin, May 28, 2017.

Tags:
  1. Zabidin

    Zabidin Well-Known Member

    Joined:
    Jan 6, 2016
    Messages:
    48
    Likes Received:
    4
    Trophy Points:
    8
    Location:
    Malaysia
    cPanel Access Level:
    Root Administrator
    Hi,

    I getting error while cron update. Below is error:
    Code:
    Update log preview:
    
    ----------------------------------------------------------------------------------------------------
    => Log opened from cPanel Update (upcp) - Slave (12902) at Sun May 28 19:23:01 2017
    [2017-05-28 19:23:01 +0800] Detected cron=1 (cron mode set from command line)
    [2017-05-28 19:23:01 +0800] 1% complete
    [2017-05-28 19:23:01 +0800] Running Standardized hooks
    [2017-05-28 19:23:01 +0800] 2% complete
    [2017-05-28 19:23:01 +0800] mtime on upcp is 1491996852 (Wed Apr 12 19:34:12 2017)
    ----------------------------------------------------------------------------------------------------
    => Log opened from /usr/local/cpanel/scripts/updatenow (12904) at Sun May 28 19:23:02 2017
    [2017-05-28 19:23:02 +0800] Detected version '11.64.0.24' from version file.
    [2017-05-28 19:23:02 +0800] Running version '11.64.0.24' of updatenow.
    [2017-05-28 19:23:03 +0800] Retrieved public key from vendor: cpanel, category: development, url: https://securedownloads.cpanel.net/cPanelDevelopmentKey.asc
    [2017-05-28 19:23:04 +0800] Retrieved public key from vendor: cpanel, category: release, url: https://securedownloads.cpanel.net/cPanelPublicKey.asc
    [2017-05-28 19:23:04 +0800] Target version set to '11.64.0.24'
    [2017-05-28 19:23:04 +0800] Up to date (11.64.0.24)
    => Log closed Sun May 28 19:23:04 2017
    [2017-05-28 19:23:04 +0800] 17% complete
    => Log closed Sun May 28 19:23:04 2017
    ----------------------------------------------------------------------------------------------------
    => Log opened from /usr/local/cpanel/scripts/maintenance (12915) at Sun May 28 19:23:05 2017
    => Log closed Sun May 28 19:23:05 2017
    ----------------------------------------------------------------------------------------------------
    => Log opened from cPanel Update (upcp) - Slave (12902) at Sun May 28 19:23:05 2017
    [2017-05-28 19:23:05 +0800] E Pre Maintenance ended, however it did not exit cleanly (256). Please check the logs for an indication of what happened
    
    The system generated this notice on Sunday, May 28, 2017 at 11:23:06 AM UTC.
    
    I already with /scripts/upcp --force but did not solve the issue. Error as below when try to force it:
    Code:
    [2017-05-29 08:52:45 +0800] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
    [2017-05-29 08:52:45 +0800] error: cannot open Packages index using db5 -  (-30973)
    [2017-05-29 08:52:45 +0800] error: cannot open Packages database in /var/lib/rpm
    [2017-05-29 08:52:45 +0800] error: rpmdb: BDB0113 Thread/process 6126/140430385104704 failed: BDB1507 Thread died in Berkeley DB library
    [2017-05-29 08:52:45 +0800] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
    [2017-05-29 08:52:45 +0800] error: cannot open Packages database in /var/lib/rpm
    [2017-05-29 08:52:45 +0800] package glibc is not installed
    [2017-05-29 08:52:45 +0800] E Blocker found: Your RPM database appears unstable. It is not possible at the moment to install a simple RPM.
    [2017-05-29 08:52:47 +0800] W An attempt to up/downgrade to 11.64.0.24 was blocked. Please review blockers.
    [2017-05-29 08:52:47 +0800] E The install encountered a fatal error: An attempt to up/downgrade to 11.64.0.24 was blocked. Please review blockers.
    => Log closed Mon May 29 08:52:47 2017
    [2017-05-29 08:52:47 +0800]   17% complete
    => Log closed Mon May 29 08:52:47 2017
    ----------------------------------------------------------------------------------------------------
    => Log opened from /usr/local/cpanel/scripts/maintenance (6414) at Mon May 29 08:52:47 2017
    => Log closed Mon May 29 08:52:48 2017
    ----------------------------------------------------------------------------------------------------
    => Log opened from cPanel Update (upcp) - Slave (6338) at Mon May 29 08:52:48 2017
    [2017-05-29 08:52:48 +0800] E Pre Maintenance ended, however it did not exit cleanly (256). Please check the logs for an indication of what happened
    => Log closed Mon May 29 08:52:51 2017
    => Log closed Mon May 29 08:52:51 2017
    [2017-05-29 08:52:52 +0800]   95% complete
    [2017-05-29 08:52:52 +0800]   Running Standardized hooks
    [2017-05-29 08:52:52 +0800]   100% complete
    [2017-05-29 08:52:52 +0800]
    [2017-05-29 08:52:52 +0800]     cPanel update completed
    [2017-05-29 08:52:52 +0800]   A log of this update is available at /var/cpanel/updatelogs/update.1496019137.log
    [2017-05-29 08:52:52 +0800]   Removing upcp pidfile
    [2017-05-29 08:52:52 +0800] W NOTE: A system upgrade was not possible due to the following blockers:
    [2017-05-29 08:52:52 +0800] W [FATAL] - Your RPM database appears unstable. It is not possible at the moment to install a simple RPM.
    => Log closed Mon May 29 08:52:52 2017
    
    What do i need to do?

    Thanks.
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,658
    Likes Received:
    1,427
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    Could you try rebuilding the RPM database via "WHM >> Software >> Rebuild RPM Database" and let us know if that fixes the issue?

    Thank you.
     
  3. Zabidin

    Zabidin Well-Known Member

    Joined:
    Jan 6, 2016
    Messages:
    48
    Likes Received:
    4
    Trophy Points:
    8
    Location:
    Malaysia
    cPanel Access Level:
    Root Administrator
    Thanks, this solve the problem.
     
    cPanelMichael and Infopro like this.
Loading...

Share This Page