cPanel process "cpanel/scripts/rpmup" process ended maturely issue

Jordy Vialoux

Member
May 10, 2019
7
1
3
London
cPanel Access Level
Root Administrator
Can anyone please advise on the error I'm getting?

I've run
Code:
/usr/local/cpanel/scripts/rpmup
and here is the following output:

Code:
checkyum version 22.3  (excludes: bind-chroot kernel ruby)
info [rpmup] Starting yum execution “--assumeyes --config /etc/yum.conf update”.
Loaded plugins: fastestmirror, universal-hooks
Setting up Update Process
Loading mirror speeds from cached hostfile
 * EA4: 91.197.228.252
 * cpanel-addons-production-feed: 91.197.228.252
 * cpanel-plugins: 91.197.228.252
 * base: mirrors.clouvider.net
 * extras: mirrors.clouvider.net
 * updates: mirrors.clouvider.net
No Packages marked for Update
info [rpmup] Completed yum execution “--assumeyes --config /etc/yum.conf update”: in 3.847 second(s).
checkyum version 22.3  (excludes: bind-chroot ruby)

Full error log:

Code:
2019-11-27 03:21:03 +0000] E    [/usr/local/cpanel/scripts/rpmup] The “/usr/local/cpanel/scripts/rpmup” command (process 25412) ended prematurely because it received the “TERM” (15) signal. The process was aborted because it reached the timeout of 3,600 seconds.
[2019-11-27 03:21:03 +0000]   The Administrator will be notified to review this output when this script completes
[2019-11-27 03:21:03 +0000]    - Finished command [ICODE]/usr/local/cpanel/scripts/rpmup[/ICODE] in 3603.004 seconds
[2019-11-27 03:21:03 +0000]   30% complete
[2019-11-27 03:21:03 +0000]    - Finished in 3603.004 seconds
[2019-11-27 03:21:09 +0000]    - Finished in 5.606 seconds
[2019-11-27 03:21:10 +0000]   Processing:
[2019-11-27 03:21:10 +0000] Maintenance complete. [state=pre]
=> Log closed Wed Nov 27 03:21:10 2019
 

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,304
1,250
313
Houston
All of that output looks normal, though I do see it took a while to complete during the update:

Code:
[2019-11-27 03:21:03 +0000]    - Finished in 3603.004 seconds
But when you ran in manually it did not experience the same issue and does not appear to have caused any further errors on the server.