cPanel Update No digest data for cpanel-exim-4.99.2-1.cp130~el9.x86_64.rpm
Answered
Today my cPanel updates suddenly started failing with the error below.
[2026-05-04 09:41:08 +1000] ***** FATAL: No digest data for cpanel-exim-4.99.2-1.cp130~el9.x86_64.rpm
[2026-05-04 09:41:08 +1000] ***** FATAL: Failed to stage “new packages” because of an error: No digest data for cpanel-exim-4.99.2-1.cp130~el9.x86_64.rpm at /usr/local/cpanel/scripts/updatenow.static-cpanelsync line 55746.
I've investigated the solution of modifying /etc/cpsources.conf, but I don't have a /etc/cpsources.conf file.
I've also run /usr/local/cpanel/scripts/check_cpanel_pkgs --fix but the problem persists.
Are there any other suggestion on how to fix this error?
-
Hi,
Same issue here updating cpanel from 134.0.20 to 134.0.23
[2026-05-04 01:26:12 +0200] ***** FATAL: Failed to stage “new packages” because of an error: No digest data for cpanel-exim-4.99.2-1.cp130~el8.x86_64.rpm at /usr/local/cpanel/scripts/updatenow.static-cpanelsync line 55746.Thanks for your incoming response
0 -
i have same problem
1 -
Same problem here, all servers.
0 -
Hey everyone - this is a known issue and the team is on it. I'll update once I know more!
1 -
same issue all servers!
0 -
Same boat here. It surely is a sync error across your mirrors.
The updates fails on cPanel 110 on CentOS 7 and on cPanel 134 on AL 8/9.
Please let us know when it is fixed.
Regards
(What a week, huh?)0 -
Update - the release team is working on this now and it should be fixed very soon. I'll post again once they're done!
0 -
We've posted an article up here: https://support.cpanel.net/hc/en-us/articles/40201497041559-Updates-to-cPanel-11-134-0-23-failing
but I'm expecting the team will have this handled in the next 15-30 minutes.
0 -
Update - issue with the mirrors is resolved at this time and we've confirmed the Exim package and updates are working well across multiple systems.
0 -
Update - the mirrors are taking a few minutes for the changes to propagate so you may see the errors linger for a few minutes if you try and update right now. I would expect things to clear up in the next 5-10 minutes.
0 -
Thanks. It works using /scripts/upcp --force, because the WHM UI somehow seems to remain cached for a while.
1 -
Thanks for the confirmation! At this point all the mirrors look good on my end, but if you see *anything* come up I'll be hanging out for a few minutes just in case.
1 -
I can confirm this issue has been resolved. UPCP to 134.0.23 was successful this time.
1 -
Kevin Kwasnik - great!
1 -
Updating 134.0.20 to 134.0.23 is working fine now.
Thanks for the quick support,
Cheers1 -
biron - glad to hear it!
0 -
Hey guys. Me again. I noticed that since this update to 110.0.112 on servers with CentOS 7, CSF started to kill a process belonging to the account "cpanellogin" due to Excessive resource usage:
Time: Mon May 4 20:17:07 2026 -0300
Account: cpanellogin
Resource: Process Time
Exceeded: 1809 > 1800 (seconds)
Executable: /usr/local/cpanel/base/show_template.stor
Command Line: /usr/local/cpanel/base/show_template.stor default_login_theme cpanel server_locale en docroot /usr/local/cpanel/base cpanel_locale
PID: 12200 (Parent PID:1362)
Killed: YesPlease confirm what is that doing and if should be whitelisted.
Also, you guys manage CSF now. You can send and update within next upcp adding the command to the whitelisted process list, right?Ready to whitelist it here when you say so. Please let me know.
0 -
I'd whitelist it for now - I'm working on a case and I'll update you soon.
0 -
I've created case CPANEL-53105 with the team and sent it over their way. I've linked this thread to the case and I'll post again once I hear more.
1 -
It looks like the time has identified the change that caused this, although it's not from the recent CSF update. We're working on a fix and I'll post again once I know more.
1 -
I think it is due to currupted or incomplete cpanel minnor package sync
0 -
cPRex : cPanel was able to upgrade without issues and is now on 110.0.119, but the cpanellogin issue persists with lfd. I'm not comfy whitelisting something that could just mask a bug. Have you guys discovered the source of error? My main worry is to be sure this not obey to an ongoing exploitation although it looks like more to something coming from coding errors in 110.0.112.
0 -
Kent Brockman - at this time we're still recommending that people just whitelist this process if it's causing an annoyance. Our plan internally will be to whitelist things so CSF doesn't detect that running process at all.
0 -
cPRex - so the solution is to mute it? Nothing bad can result by doing that?
Is then normal for the cpanellogin process to remain resident?0 -
Correct - that runs on the older CentOS 7 machines and CSF can just ignore it.
0
Please sign in to leave a comment.
Comments
25 comments