Failed to retrieve Package from Cloudlinux error
Hi, I wonder if you can help me please?
I've just received an email from my server with the above problem reported. Running /usr/local/cpanel/scripts/rpmup I get the following output:
Is there anything I can do to prevent the error recurring? Thanks
checkyum version 22.3 (excludes: bind-chroot kernel ruby)
info [rpmup] Starting yum execution "--assumeyes --config /etc/yum.conf update".
Loaded plugins: fastestmirror, rhnplugin, tsflags, universal-hooks
This system is receiving updates from CLN.
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
Excluding mirror: cl-mirror.vimexx.nl
* cloudlinux-x86_64-server-7: cl-mirror.fr.planethoster.net
Resolving Dependencies
--> Running transaction check
---> Package python-perf.x86_64 1:3.10.0-962.3.2.lve1.5.26.4.el7 will be updated
---> Package python-perf.x86_64 1:3.10.0-962.3.2.lve1.5.26.5.el7 will be an update
--> Finished Dependency Resolution
Total download size: 1.7 M
Downloading packages:
No Presto metadata available for cloudlinux-x86_64-server-7
info [rpmup] Completed yum execution "--assumeyes --config /etc/yum.conf update": in 21.929 second(s).
(XID pwzn57) The system failed to execute yum with the arguments "--assumeyes --config /etc/yum.conf update" because of an error: The "/usr/bin/yum --assumeyes --config /etc/yum.conf update" command (process 3856444) reported error number 1 when it ended. :
Error downloading packages:
1:python-perf-3.10.0-962.3.2.lve1.5.26.5.el7.x86_64: failed to retrieve getPackage/python-perf-3.10.0-962.3.2.lve1.5.26.5.el7.x86_64.rpm from cloudlinux-x86_64-server-7
error was [Errno 14] HTTPS Error 404 - Not Found
checkyum version 22.3 (excludes: bind-chroot ruby)Is there anything I can do to prevent the error recurring? Thanks
-
This problem may be due to network disturbances. However, it is clear from the error text that the file is not found in this address. It is best to use the following command first and then try again. yum update all -y 0 -
Thanks - I tried it but get the report No Match for argument: all No package all available. No packages marked for update0 -
yum update all
is incorrect it'd just be:yum update
You might try running:yum clean all yum -y update0 -
Hi Lauren, Thanks for stepping in. I ran the second and all went well until I got towards the end when I had an error: Cleanup : kmod-libs-20-21.el7.x86_64 9/9 grep: /boot/grub2/grub.cfg: No such file or directory grep: /boot/grub2/grub.cfg: No such file or directory grep: /boot/grub2/grub.cfg: No such file or directory [WARNING] GRUB config file is missing Regenerating GRUB configuration... [SUCCESS] GRUB config has been restored [WARNING] Kernel 3.10.0-962.3.2.lve1.5.26.5.el7.x86_64 GRUB entry is missing [ERROR] Kernel 3.10.0-962.3.2.lve1.5.26.5.el7.x86_64 initramfs GRUB entry is missing and cannot be automatically added due to unknown reasons, please fix GRUB config manually !!!! /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache is not executable
The final message was that it was a success! I'm not sure what i should do next!0 -
Do you know if it was able to actually restore the grub.cfg? stat /boot/grub2/grub.cfg
Either way, for this issue, if you have a CloudLinux License with us I'd suggest opening a ticket with us. Otherwise you'd want to open a ticket with them directly here: CloudLinux - Main | New template0 -
Do you know if it was able to actually restore the grub.cfg?
stat /boot/grub2/grub.cfg
Either way, for this issue, if you have a CloudLinux License with us I'd suggest opening a ticket with us. Otherwise you'd want to open a ticket with them directly here:
Yes, I have a CloudLinux License with you. I'll open a ticket. Thanks for your help.0 -
Hi @KenCope Feel free to add the ticket ID here and I'll update the thread with the outcome. 0 -
Hi @KenCope Feel free to add the ticket ID here and I'll update the thread with the outcome.
Hi Lauren, Thannks - 134811890 -
Hi @KenCope As it turns out CloudLinux will warn about the presence of grub2 whether or not the system uses it, in this case you were using grub not grub2 and there aren't any issues. To stop the error being reported the Technician added a symlink from grub2->grub. 0
Please sign in to leave a comment.
Comments
9 comments