Operating System & Version
CENTOS 7.8
cPanel & WHM Version
90.0.18

masterross

Well-Known Member
Apr 7, 2004
73
5
158
Hi,
I'm getting issue with the latest stable update

=> Log opened from cPanel Update (upcp) - Slave (6983) at Sun Dec 13 11:53:36 2020
[2020-12-13 11:53:36 +0200] Pre Maintenance completed successfully
[2020-12-13 11:53:37 +0200] 95% complete
[2020-12-13 11:53:37 +0200] Running Standardized hooks
[2020-12-13 11:53:37 +0200] 100% complete
[2020-12-13 11:53:37 +0200]
[2020-12-13 11:53:37 +0200] cPanel update completed
[2020-12-13 11:53:37 +0200] A log of this update is available at /var/cpanel/updatelogs/update.1607852251.log
[2020-12-13 11:53:37 +0200] Removing upcp pidfile
[2020-12-13 11:53:37 +0200] W NOTE: A system upgrade was not possible due to the following blockers:
[2020-12-13 11:53:37 +0200] W [FATAL] - Your RPM database appears unstable. It is not possible at the moment to install a simple RPM.
[2020-12-13 11:53:37 +0200] W [FATAL] - This system is running an outdated version of OpenSSL (package openssl is not installed), which will need to be updated to at least 1.0.2e to continue.
=> Log closed Sun Dec 13 11:53:37 2020
[root@wipm019 ~]# openssl version
OpenSSL 1.0.2k-fips 26 Jan 2017

OpenSSL is handle by EasyApache, right?

Where is the problem?
 
Last edited by a moderator:

andrew.n

Well-Known Member
Jun 9, 2020
982
363
63
EU
cPanel Access Level
Root Administrator
The problem is that cPanel can't install the new OpenSSL package for some reason probably due to yum being corrupted. What does yum update shows? Any errors?

Try to rebuild the rpm db with:

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

then run cPanel update again
 
  • Like
Reactions: masterross

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
16,598
2,620
363
cPanel Access Level
Root Administrator
Just to review, the core problem here was this line of the update log that you provided"

"Your RPM database appears unstable. It is not possible at the moment to install a simple RPM."

This indicates an issue with Yum itself, specifically with the RPM database. Running the commands that @andrew.n provided will attempt to rebuild the RPM database, although that work can also be done through the WHM >> Rebuild RPM Database page.

I'm glad that's all it was and that things are working well now!
 
  • Like
Reactions: masterross