upcp fails so service SSLs can't be renewed
I have an old server that is in the process of being migrated away from. It's on CL7 and WHM 110 still. Lately upcp has been failing, and since the service SSLs are renewed from there, they have expired. Is it possible to trigger the service SSLs to renew outside of upcp?
-
Hey there! Yes, you can run the following command anytime to get the hostname SSL renewed:
/usr/local/cpanel/bin/checkallsslcerts
If you could share the reason for the upcp failure I may be able to help with that as well.
0 -
That worked, thanks.
I assumed the upcp failures were due to the age of the OS. Here is the log preview from the email:
[2025-04-30 01:22:26 -0400] Child: 2: Stage File: /var/tmp/5675.ANEL_SCRIPTS_UPDATENOW_STATIC_CPANELSYNC__.fe316700.tmp
[2025-04-30 01:22:26 -0400] Child 5932 created to stage files.
[2025-04-30 01:22:26 -0400] Retrieving and staging /cpanelsync/11.110.0.58/jupiter/dynamicui.conf.xz
[2025-04-30 01:22:26 -0400] Retrieving and staging /cpanelsync/11.110.0.58/jupiter/_assets/_ajaxapp_header.gradients.static.bz2
[2025-04-30 01:22:26 -0400] Using mirror '209.133.199.70' for host 'httpupdate.cpanel.net'.
[2025-04-30 01:22:26 -0400] Using mirror '209.133.199.70' for host 'httpupdate.cpanel.net'.
=> Log closed Wed Apr 30 01:22:26 2025
=> Log closed Wed Apr 30 01:22:26 2025
[2025-04-30 01:22:26 -0400] Sync child 5931 exited cleanly.
[2025-04-30 01:22:26 -0400] Sync child 5932 exited cleanly.
[2025-04-30 01:22:26 -0400] All files Staged
[2025-04-30 01:22:51 -0400] 35 packages excluded due to repository priority protections
[2025-04-30 01:22:58 -0400] No package boost169-program-options available.
[2025-04-30 01:22:59 -0400] W Error: Nothing to do
[2025-04-30 01:23:00 -0400] Completed yum execution “--assumeyes --color=never --config /etc/yum.conf install boost169-program-options”: in 53.179 second(s).
[2025-04-30 01:23:00 -0400] E (XID 2h7d6x) “/usr/bin/yum” reported error code “1” when it ended:
[2025-04-30 01:23:00 -0400] E Sysup: Needed system packages were not installed: boost169-program-options
=> Log closed Wed Apr 30 01:23:00 2025
=> Log closed Wed Apr 30 01:23:00 2025
[2025-04-30 01:23:00 -0400] E Blocker found: Cannot upgrade to 11.110.0.58 until needed system packages are installed.
[2025-04-30 01:23:00 -0400] Removing staged files and directories for binaries/linux-c7-x86_64, cpanel
[2025-04-30 01:23:00 -0400] Removing staged files and directories for jupiter
[2025-04-30 01:23:00 -0400] E The install encountered a fatal error: Cannot upgrade to 11.110.0.58 until needed system packages are installed.
=> Log closed Wed Apr 30 01:23:00 2025
[2025-04-30 01:23:00 -0400] 17% complete0 -
Thanks for that - you should be able to take care of the upcp error with this information;
0 -
Thanks, that cleared up that particular issue. But I still have this issue.
[2025-04-30 21:46:48 -0400] E [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages” command (process 31956) reported error number 1 when it ended.
...
[2025-04-30 21:46:48 -0400] The Administrator will be notified to review this output when this script completes
[2025-04-30 21:46:48 -0400] - Finished command `/usr/local/cpanel/scripts/update-packages` in 39.054 seconds
[2025-04-30 21:46:48 -0400] 30% complete
[2025-04-30 21:46:48 -0400] - Finished in 39.054 seconds
[2025-04-30 21:46:48 -0400] - Finished in 0.099 seconds
[2025-04-30 21:46:48 -0400] Processing:
[2025-04-30 21:46:48 -0400] Maintenance complete. [state=pre]
=> Log closed Wed Apr 30 21:46:48 2025
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (29888) at Wed Apr 30 21:46:48 20250 -
What happens when you run "yum update" on the machine?
0 -
I get the following error:
Error: Package: alt-python35-yara-3.5.0-11.el7.x86_64 (@cloudlinux-imunify360)
Requires: libyara.so.3()(64bit)
Removing: yara-3.5.0-5.el7.x86_64 (@cloudlinux-imunify360)
libyara.so.3()(64bit)
Updated By: yara-4.1.3-1.el7.x86_64 (epel)
~libyara.so.8()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest0 -
There could be several repository issues you end up needing to work through on an older system. Here is that specific one:
0 -
Thanks. yum update completes successfully now.
0 -
I'm glad to hear that's working well now!
0
Please sign in to leave a comment.
Comments
9 comments