Latest activity

looks like yum update is able to be accessed from the server [root@host5 ~]# yum check-update Last metadata expiration check: 3:16:50...

I agree. I usually install the new kernel using yum update but that is not working I have a lot of blocked IP ranges in the CSF...

It does not look like you've got the new kernel installed at all

[root@host5 ~]# df -h -T Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev tmpfs tmpfs 16G 0 16G...

What do you have? df -h -T? rpm -qa | grep ^kernel | sort -V?

boot loader entries does not show the new kernel [root@host5 ~]# ls -l /boot/loader/entries/* -rw-r--r--. 1 root root 516 Apr 4 2024...

the output does not show which index is selected for loading, it only shows that your current kernel is still on the index=0

[root@host5 ~]# grubby --info="/boot/vmlinuz-$(uname -r)" index=0 kernel="/boot/vmlinuz-5.14.0-570.49.1.el9_6.x86_64" args="ro...

Check grubby output to make sure a new kernel is selected now and see which kernel is selected for booting.

server did not load the new kernel

Did the server load the new kernel or not?

[root@host5 ~]# sudo grub2-mkconfig -o /boot/grub/grub.cfg /sbin/grub2-mkconfig: line 286: /boot/grub/grub.cfg.new: No such file or...

You might try and re-generate /boot/grub2/grub.cfg, of course if you use Grub2

[root@host5 ~]# grubby --info="/boot/vmlinuz-$(uname -r)" index=0 kernel="/boot/vmlinuz-5.14.0-570.49.1.el9_6.x86_64" args="ro...

It seems you did not specify flags for the command, the command if used without flags, reports: [root@server ~]# grubby grubby: no...