Getting "Error: Failed to download metadata for repo 'imunify360': Yum repo downloading error: Downloading error(s): "
Hi,
I've been getting these emails periodically, so emailing to enquire why I'm getting it:
Part of message:
New Security Advisor notifications with Medium importance
Type Module Advice
⚠ Medium Kernel The system cannot check the kernel status: “/usr/bin/yum” reported error code “1” when it ended: Error: Failed to download metadata for repo 'imunify360': Yum repo downloading error: Downloading error(s): repodata/811c1539ce270053292e0f5630f9c12e1594c8e487a3ed9c4306dadcb0815c73-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/f621d2029608d31e8976fe9edc4a885297a7f4afb25d24ef0368fa20c0009074-filelists.xml.gz - Cannot download, all mirrors were already tried without success
In order to resolve these security concerns, log in to WHM and navigate to the “Security Advisor” interface.
Do I need imunify360? I'm not subscribed to it.
It's failed to download, what's the solution?
Kind regards,
Leon
-
By the way, I'm using the following operating system if that helps:
AlmaLinux v8.9.0 STANDARD kvm
cPanel Version 118.0.80 -
Im getting this too, since today. Im using Almalinux 8.90
Ive been seeing the updates are very slow since last week.
0 -
Hey there! What happens if you run a basic "yum update" on the server? It's possible there was just a temporary issue with that mirror, but if Yum is working outside the automated notification things are likely fine.
0 -
Hi,
It runs fine.
It seems to periodically happens so thought I will ask.
I will keep an eye out for it but if it happens again I will update the thread.
Here was the following output:
yum update
Last metadata expiration check: 1:24:13 ago on Tue 23 Apr 2024 02:56:29 PM BST.
Dependencies resolved.
==================================================================================================================================
Package Architecture Version Repository Size
==================================================================================================================================
Installing:
kernel x86_64 4.18.0-513.24.1.el8_9 baseos 10 M
kernel-core x86_64 4.18.0-513.24.1.el8_9 baseos 43 M
kernel-modules x86_64 4.18.0-513.24.1.el8_9 baseos 36 M
Removing:
kernel x86_64 4.18.0-477.10.1.el8_8 @System 0
kernel-core x86_64 4.18.0-477.10.1.el8_8 @System 70 M
kernel-modules x86_64 4.18.0-477.10.1.el8_8 @System 25 MTransaction Summary
==================================================================================================================================
Install 3 Packages
Remove 3 PackagesTotal download size: 89 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): kernel-4.18.0-513.24.1.el8_9.x86_64.rpm 18 MB/s | 10 MB 00:00
(2/3): kernel-modules-4.18.0-513.24.1.el8_9.x86_64.rpm 30 MB/s | 36 MB 00:01
(3/3): kernel-core-4.18.0-513.24.1.el8_9.x86_64.rpm 29 MB/s | 43 MB 00:01
-----------------------------------------------------------------------------------------------------------------------------------------------
Total 28 MB/s | 89 MB 00:03
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : kernel-core-4.18.0-513.24.1.el8_9.x86_64 1/6
Running scriptlet: kernel-core-4.18.0-513.24.1.el8_9.x86_64 1/6
Installing : kernel-modules-4.18.0-513.24.1.el8_9.x86_64 2/6
Running scriptlet: kernel-modules-4.18.0-513.24.1.el8_9.x86_64 2/6
Installing : kernel-4.18.0-513.24.1.el8_9.x86_64 3/6
Erasing : kernel-4.18.0-477.10.1.el8_8.x86_64 4/6
Running scriptlet: kernel-4.18.0-477.10.1.el8_8.x86_64 4/6
Erasing : kernel-modules-4.18.0-477.10.1.el8_8.x86_64 5/6
Running scriptlet: kernel-modules-4.18.0-477.10.1.el8_8.x86_64 5/6
Running scriptlet: kernel-core-4.18.0-477.10.1.el8_8.x86_64 6/6
Erasing : kernel-core-4.18.0-477.10.1.el8_8.x86_64 6/6
Running scriptlet: kernel-core-4.18.0-477.10.1.el8_8.x86_64 6/6
Running scriptlet: kernel-core-4.18.0-513.24.1.el8_9.x86_64 6/6
Running scriptlet: kernel-modules-4.18.0-513.24.1.el8_9.x86_64 6/6
Running scriptlet: kernel-core-4.18.0-477.10.1.el8_8.x86_64 6/6
Verifying : kernel-4.18.0-513.24.1.el8_9.x86_64 1/6
Verifying : kernel-core-4.18.0-513.24.1.el8_9.x86_64 2/6
Verifying : kernel-modules-4.18.0-513.24.1.el8_9.x86_64 3/6
Verifying : kernel-4.18.0-477.10.1.el8_8.x86_64 4/6
Verifying : kernel-core-4.18.0-477.10.1.el8_8.x86_64 5/6
Verifying : kernel-modules-4.18.0-477.10.1.el8_8.x86_64 6/6Installed:
kernel-4.18.0-513.24.1.el8_9.x86_64 kernel-core-4.18.0-513.24.1.el8_9.x86_64 kernel-modules-4.18.0-513.24.1.el8_9.x86_64
Removed:
kernel-4.18.0-477.10.1.el8_8.x86_64 kernel-core-4.18.0-477.10.1.el8_8.x86_64 kernel-modules-4.18.0-477.10.1.el8_8.x86_64Complete!
0 -
Thanks for the additional details. There are likely a number of Imunify360 packages on the server, which you can see with this command:
rpm -qa | grep -i imunify
You also would be able to see the repositories inside the /etc/yum.repos.d directory.
It sounds like this was just a temporary glitch with either networking or those repositories, so I would not be concerned at this point. If it does happen again, let us know!
0 -
OK. I will keep an open eye and report back if it does.
1
Please sign in to leave a comment.
Comments
6 comments