Security Advisor Notification Kernel imunify360
Hi, i received this notice.
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/(removed by me)-primary.xml.gz - Cannot download, all mirrors were already tried without success
Im thinking that this is because kernel care cannot connect to check and update my kernel because i have host access limited to my dedicated local IP address. Does that sound correct?
If so i guess i need to contact them to find out how they are connecting so i can add the connection data to host access allow.
Does this sound logical, am i on the right track here, or does that message mean something else?
Thanks :)
-
Hey there! That could be the case, sure - can you let me know what you mean y "host access limited" in this case? You should be able to reproduce this error with a "yum update" for testing purposes.
0 -
Thanks, ok i will try the yum update for testing but i would not be shocked it if worked because i am using my dedicated ip from my ISP. I did not intentionally set out to block kernel version checking. To answer your question to harden my server a few months ago i limited my host access to only my dedicated IP from my ISP because i am the only user on the server. This is the first issue i have noticed from doing so. I did contact kernel care to see what they can offer.
Update: ran system update it worked fine, but again i logged into WHM via my dedicated IP from my ISP.
Here is the log from the update.
System update has run successfully.
System update process has started. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: kernel x86_64 4.18.0-553.30.1.el8_10 baseos 10 M Installing dependencies: kernel-core x86_64 4.18.0-553.30.1.el8_10 baseos 43 M kernel-modules x86_64 4.18.0-553.30.1.el8_10 baseos 36 M Removing: kernel x86_64 4.18.0-513.5.1.el8_9 @anaconda 0 kernel-core x86_64 4.18.0-513.5.1.el8_9 @anaconda 71 M kernel-modules x86_64 4.18.0-513.5.1.el8_9 @anaconda 25 M Transaction Summary ================================================================================ Install 3 Packages Remove 3 Packages Total download size: 90 M Downloading Packages: (1/3): kernel-4.18.0-553.30.1.el8_10.x86_64.rpm 7.0 MB/s | 10 MB 00:01 (2/3): kernel-modules-4.18.0-553.30.1.el8_10.x8 9.0 MB/s | 36 MB 00:04 (3/3): kernel-core-4.18.0-553.30.1.el8_10.x86_6 9.4 MB/s | 43 MB 00:04 -------------------------------------------------------------------------------- Total 18 MB/s | 90 MB 00:04 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : kernel-core-4.18.0-553.30.1.el8_10.x86_64 1/6 Running scriptlet: kernel-core-4.18.0-553.30.1.el8_10.x86_64 1/6 Installing : kernel-modules-4.18.0-553.30.1.el8_10.x86_64 2/6 Running scriptlet: kernel-modules-4.18.0-553.30.1.el8_10.x86_64 2/6 Installing : kernel-4.18.0-553.30.1.el8_10.x86_64 3/6 Running scriptlet: kernel-4.18.0-513.5.1.el8_9.x86_64 4/6 Erasing : kernel-4.18.0-513.5.1.el8_9.x86_64 4/6 Running scriptlet: kernel-4.18.0-513.5.1.el8_9.x86_64 4/6 Erasing : kernel-modules-4.18.0-513.5.1.el8_9.x86_64 5/6 Running scriptlet: kernel-modules-4.18.0-513.5.1.el8_9.x86_64 5/6 Running scriptlet: kernel-core-4.18.0-513.5.1.el8_9.x86_64 6/6 Erasing : kernel-core-4.18.0-513.5.1.el8_9.x86_64 6/6 Running scriptlet: kernel-core-4.18.0-513.5.1.el8_9.x86_64 6/6 Running scriptlet: kernel-core-4.18.0-553.30.1.el8_10.x86_64 6/6 Running scriptlet: kernel-modules-4.18.0-553.30.1.el8_10.x86_64 6/6 Running scriptlet: kernel-core-4.18.0-513.5.1.el8_9.x86_64 6/6 Verifying : kernel-4.18.0-553.30.1.el8_10.x86_64 1/6 Verifying : kernel-core-4.18.0-553.30.1.el8_10.x86_64 2/6 Verifying : kernel-modules-4.18.0-553.30.1.el8_10.x86_64 3/6 Verifying : kernel-4.18.0-513.5.1.el8_9.x86_64 4/6 Verifying : kernel-core-4.18.0-513.5.1.el8_9.x86_64 5/6 Verifying : kernel-modules-4.18.0-513.5.1.el8_9.x86_64 6/6 Installed: kernel-4.18.0-553.30.1.el8_10.x86_64 kernel-core-4.18.0-553.30.1.el8_10.x86_64 kernel-modules-4.18.0-553.30.1.el8_10.x86_64 Removed: kernel-4.18.0-513.5.1.el8_9.x86_64 kernel-core-4.18.0-513.5.1.el8_9.x86_64 kernel-modules-4.18.0-513.5.1.el8_9.x86_64 Complete! System update process has finished.
System update has run successfully.
0 -
Thanks for confirming that Yum itself is working properly. I'm assuming that initial error came from the nightly update, correct? If so, can you run "/scripts/upcp --force" to see if that gives you any additional errors?
0 -
hi, i ran /scripts/upcp --force and it says completed all updates. Does that last log entry cover everything or do i need to check out each log section for errors?
Not sure how often that checks for kernel version but maybe the best thing to do is to wait to see if it happens again since all tests so far work. Your thoughts ?
0 -
Yes, if the upcp completed everything is working well. My guess is that there was just a temporary issue with the mirrors, I would have expected both Yum and upcp to fail if there was a problem with that repository still.
As far as the kernel update, that gets checked nightly as part of the update process.
0
Please sign in to leave a comment.
Comments
5 comments