All my systems are failing to update due to yum missing digest
All of my servers, in different data centers with totally different IPs, and some CentOS, some RHEL, are failing updates with the error:
[QUOTE]cPanel version change from "11.102.0.11" to "11.102.0.12" failed during updatenow.
FATAL: No digest data for cpanel-php74-7.4.29-1.cp11102.x86_64.rpm
I haven't seen anyone else posting about this. What do I do?
I haven't seen anyone else posting about this. What do I do?
-
All of my servers, in different data centers with totally different IPs, and some CentOS, some RHEL, are failing updates with the error: I haven't seen anyone else posting about this. What do I do?
try running this in terminal : go to whm > terminal then type in:/usr/local/cpanel/scripts/check_cpanel_pkgs
and tell me if it reports anything? or just type in this:/usr/local/cpanel/scripts/check_cpanel_pkgs --fix0 -
[root@cpanel03 ~]# less /etc/cpsources.conf /etc/cpsources.conf: No such file or directory [root@cpanel03 ~]# /usr/local/cpanel/scripts/check_cpanel_pkgs [root@cpanel03 ~]#0 -
Same here on one of my systems, Centos 7.9. No cpsources.conf file, check pkgs reveals nothing. 0 -
There were some mirror issues earlier today, but at this point I believe that is all taken care of. Can you try the updates again and let me know if you still see issues? 0 -
Hi, I think this is not resolved yet. Some update mirrors are still having issues. Multiple customers reported this and still reporting it. I'm attaching a screenshot of the most recent ticket we handled a few hours back. Also, commenting the entry in /etc/cpsources.conf is not the solution here. You need to add a working update Mirror here. I'm pasting the recent ticket that we handled for reference. ----------------------------------------------------------------------------------------------------------------------------------------------- I was able to replicate the issue and found the following error in the log files. [QUOTE]root@:/var/cpanel/updatelogs# tail -10 update.168322.1075503.1650879353.log [2022-04-25 12:35:26 +0000] The Administrator will be notified to review this output when this script completes [2022-04-25 12:35:26 +0000] ***** FATAL: Failed to stage "new packages" because of an error: No digest data for cpanel-php74/cpanel-php74_7.4.29-1.cp11102_amd64.deb at /usr/local/cpanel/scripts/updatenow.static-cpanelsync line 50068. [2022-04-25 12:35:26 +0000] : see I then created cpsources.conf and specified a custom mirror as follows. [QUOTE]root@:/var/cpanel/updatelogs# cat /etc/cpsources.conf HTTPUPDATE=184.94.196.92
Then tried the update and that resolved the issue. Please check the log given below to verify. [QUOTE]root@:/var/cpanel/updatelogs# tail -10 /var/cpanel/updatelogs/update.168732.1093493.1650879353.log [2022-04-25 12:41:45 +0000] 95% complete [2022-04-25 12:41:45 +0000] Running Standardized hooks [2022-04-25 12:41:45 +0000] 100% complete [2022-04-25 12:41:45 +0000] [2022-04-25 12:41:45 +0000] cPanel update completed [2022-04-25 12:41:45 +0000] A log of this update is available at /var/cpanel/updatelogs/update.168732.1093493.1650879353.log [2022-04-25 12:41:45 +0000] Removing upcp pidfile [2022-04-25 12:41:45 +0000] [2022-04-25 12:41:45 +0000] Completed all updates => Log closed Mon Apr 25 12:41:45 2022
Your cPanel is now updated to the latest version [QUOTE]root@:/var/cpanel/updatelogs# cat /usr/local/cpanel/version 11.102.0.12
Please review and do get back to us if you need any further help in this regard.0 -
@ServerHealers - I've passed this along to our team - thanks so much! 0 -
Confirmed, manually creating and setting to that IP in /etc/cpsources.conf solved for me. Thanks @ServerHealers! 0 -
There were some mirror issues earlier today, but at this point I believe that is all taken care of. Can you try the updates again and let me know if you still see issues?
This has been going on at least since April 21. I haven't tried forcing mirrors yet.0 -
Update - the mirror issue has officially been resolved now, including the one I mentioned earlier. @yakatz9 - I suppose it's possible that it could have been ongoing longer, but a vast majority of the reports were within the last 24 hours. 0 -
We have the Same Issue. 0 -
@risecompany - if you try the update now are you still seeing problems? 0 -
Hello, we have the same problem: ***** FATAL: No digest data for cpanel-php74-7.4.29-1.cp11102.x86_64.rpm ***** FATAL: Failed to stage "new packages" because of an error: No digest data for cpanel-php74-7.4.29-1.cp11102.x86_64.rpm at /usr/local/cpanel/scripts/updatenow.static-cpanelsync line 50068. Thanks! 0 -
@risecompany - if you try the update now are you still seeing problems?
Yes, The same issue is still. [QUOTE] [2022-04-25 22:44:30 +0200] : see RPM Installation Failures | cPanel & WHM Documentation for more information [2022-04-25 22:44:30 +0200] The Administrator will be notified to review this output when this script completes [2022-04-25 22:44:30 +0200] Removing staged files and directories for binaries/linux-c7-x86_64, cpanel => Log closed Mon Apr 25 22:44:30 2022 [2022-04-25 22:44:30 +0200] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.5397.140112193.1649518343.log` failed, exited with code 13 (signal = 0) => Log closed Mon Apr 25 22:44:30 20220 -
I am also still seeing it. Two systems I just checked say [QUOTE]Using mirror '63.247.64.58' for host 'httpupdate.cpanel.net'. 0 -
Thanks for the reports - I've let our team know about these and linked them this thread. They'll take another look at this, but it will likely get fixed after I leave my shift for today, but I'll post an update once I have one. 0 -
I can confirm when I set [QUOTE]HTTPUPDATE=184.94.196.92
the update works, so it does seem to be bad mirrors.0 -
Yes, 184.94.196.92 will work for both Ubuntu and CentOS based cPanel servers. It's because cPanel is using the same mirror servers for all OS types. E.g.: So, if anyone has similar issues, it's safe to use 184.94.196.92 in cpsources.conf, as a temporary fix until cPanel resolves this issue. I can confirm when I set the update works, so it does seem to be bad mirrors.
0 -
I have a DNSOnly server that does not have a /etc/cpsources.conf file. Where do I find the file to add this to? HTTPUPDATE=184.94.196.92 Jim 0 -
I wouldn't recommend manually working around the issue. Once we resolve the mirror issues the updates will work like normal and you won't have to revert any changes. 0 -
I have a DNSOnly server that does not have a /etc/cpsources.conf file. Where do I find the file to add this to? HTTPUPDATE=184.94.196.92 Jim
Never mind. I created a new /etc/cpsources.conf file with one line HTTPUPDATE=184.94.196.92 That worked. Jim0 -
I have a DNSOnly server that does not have a /etc/cpsources.conf file. Where do I find the file to add this to? HTTPUPDATE=184.94.196.92 Jim
Create the file So if you do nano /etc/cpsources.conf Then add HTTPUPDATE=184.94.196.92 Then do ctrl X Then select Y for yes and hit enter Then you should be good and try again0 -
Where do I find the file to add this to? HTTPUPDATE=184.94.196.92
Create it with just that content.0 -
many of our servers are showing up the same error when trying to update. 0 -
many of our servers are showing up the same error when trying to update.
have you tried to create that file and add the HTTPD ip as others then try the upgrade again ?0 -
FYI, during nightly update upcp failed. [QUOTE][2022-04-25 23:02:47 -0400] E [/usr/local/cpanel/scripts/findphpversion] "/usr/local/cpanel/bin/python-packman" reported error code "1" when it ended: Could not retrieve mirrorlist
So I commented out the hardcoded IP and re-ran and it worked without error.0 -
Using this solution I was able to complete the update. But for some reason I can't access WHM using the web interface. 0 -
@Popetrix - not being able to access WHM would be a separate issue. I'd recommend checking the cPanel error logs to see if there is anything useful there. There are still mirror issues today and we're still working on it on our side. I'll post an update once I have one. 0 -
have you tried to create that file and add the HTTPD ip as others then try the upgrade again ?
Since Cpanel representative recommended not doing that change, we didn't. today we re-tried the update and almost all completed without problems, only 1 server not. retried later and it worked.0 -
It's not so much that the change would hurt anything, it's just something else that could end up left in place and cause confusion after you forget about it in a year when you run into another issue. At this time our team has done some additional testing and we're no longer seeing issues on our end. Please post if you see any failures after this point. 0
Please sign in to leave a comment.
Comments
35 comments