SOLVED cPanel & WHM update failure in upcp script

Operating System & Version
CENTOS 7.5 virtuozzo
cPanel & WHM Version
v86.0.20

andinacom

Member
Mar 23, 2015
8
0
1
ecuador
cPanel Access Level
DataCenter Provider
Hi, this night, this error came to me for the first time:

----------------------------------------------------------
Maintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/rpmup”. Review the update logs to determine why the update failed.


Update log preview:
...
...
[2020-05-16 05:40:28 +0200] E [/usr/local/cpanel/scripts/rpmup] The “/usr/local/cpanel/scripts/rpmup” command (process 13667) reported error number 1 when it ended.
...
[2020-05-16 05:41:23 +0200] - Finished command `/usr/local/cpanel/scripts/check_mysql` in 0.172 seconds
[2020-05-16 05:41:23 +0200] Processing: Checking CloudLinux installation
[2020-05-16 05:41:23 +0200] - Processing command `/usr/local/cpanel/bin/cloudlinux_update`
[2020-05-16 05:41:23 +0200] - Finished command `/usr/local/cpanel/bin/cloudlinux_update` in 0.062 seconds
[2020-05-16 05:41:23 +0200] Processing: Updating plugins data cache
[2020-05-16 05:41:23 +0200] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache`
[2020-05-16 05:41:23 +0200] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.044 seconds
[2020-05-16 05:41:23 +0200] Processing: Ensuring SSL certificate information for CCS is up to date.
[2020-05-16 05:41:23 +0200] - Processing command `/usr/local/cpanel/scripts/ccs-check --run --ssl`
[2020-05-16 05:41:23 +0200] - Finished command `/usr/local/cpanel/scripts/ccs-check --run --ssl` in 0.011 seconds
[2020-05-16 05:41:23 +0200] Processing: Ensure cpanel-plugins yum repo exists
[2020-05-16 05:41:24 +0200] - Finished in 0.729 seconds
[2020-05-16 05:41:24 +0200] Processing: Checking Addon Licenses
[2020-05-16 05:41:24 +0200] - Finished in 0.014 seconds
[2020-05-16 05:41:24 +0200] Processing: Checking End Of Life for current version.
[2020-05-16 05:41:24 +0200] - Finished in 0.100 seconds
[2020-05-16 05:41:24 +0200] Processing:
[2020-05-16 05:41:24 +0200] Maintenance complete.
=> Log closed Sat May 16 05:41:24 2020
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (13227) at Sat May 16 05:41:24 2020

I manually ran the command "/usr/local/cpanel/scripts/rpmup" and in the end I get these two errors (bold):
------------------------------------------------------------
....
Removing postfix.x86_64 2:2.10.1-9.el7 - u due to obsoletes from installed exim-4.93-2.cp1186.x86_64
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package postfix.x86_64 2:2.10.1-9.el7 will be installed
--> Processing Dependency: postfix = 2:2.10.1-9.el7 for package: 2:postfix-sysvinit-2.10.1-9.el7.noarch
--> Finished Dependency Resolution
Error: Package: 2:postfix-sysvinit-2.10.1-9.el7.noarch (base)
You could try using --skip-broken to work around the problem
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
cpanel-analytics-1.3.3-1.1.noarch has missing requires of cpanel-version >= ('0', '73.0.0', None)
info [rpmup] Completed yum execution “--assumeyes --config /etc/yum.conf update”: in 9.179 second(s).
(XID hb2n73) “/usr/bin/yum” reported error code “1” when it ended:
checkyum version 22.3 (excludes: bind-chroot ruby)
-------------------------------------------------------------
Can you help me solve the problem?
Thank's a lot, Alex
 
Last edited by a moderator:

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,297
1,251
313
Houston
The package in question isn't something we provide. You may try removing that package with the following:

yum remove postfix-sysvinit

rpm -e --nodeps postfix-sysvinit
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
795
110
168
cPanel Access Level
Root Administrator
Great - I'm glad to hear that's working well for you now.

When you see the error with the /scripts/rpmup command, I always like to do a "yum update" command on the system to confirm if the error is outside of the cPanel system, as that might give you more detail than what is available in the cPanel update logs.
 
  • Like
Reactions: cPanelLauren