Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WHM v68.0.16 - You must reboot the server to apply kernel updates

Discussion in 'General Discussion' started by sadasan, Nov 23, 2017.

  1. sadasan

    sadasan Active Member

    Joined:
    Feb 10, 2015
    Messages:
    26
    Likes Received:
    2
    Trophy Points:
    3
    cPanel Access Level:
    Root Administrator
    Hello,

    WHM v68.0.16 plus KernelCare

    I am still seeing the warning message of "You must reboot the server to apply kernel updates" at the right top portion of WHM.

    When is this issue fixed?
    Any advice would be appreciated.
    cPanel_reboot.jpg
    Thanks.
     
    #1 sadasan, Nov 23, 2017
    Last edited by a moderator: Nov 23, 2017
  2. SysSachin

    SysSachin Well-Known Member

    Joined:
    Aug 23, 2015
    Messages:
    604
    Likes Received:
    41
    Trophy Points:
    28
    Location:
    India
    cPanel Access Level:
    Root Administrator
    Twitter:
    Did you try to reboot the server, and after rebooting still you get the error ?
     
  3. pecoraridigital

    pecoraridigital Registered

    Joined:
    Nov 24, 2017
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brazil
    cPanel Access Level:
    Root Administrator
    Hello,
    I have the same problem. I forced the reinstallation of the Cpanel and even then it did not help.

    Do you have any ideas?
     
  4. JawadArshad

    JawadArshad Well-Known Member
    PartnerNOC

    Joined:
    Apr 8, 2008
    Messages:
    457
    Likes Received:
    6
    Trophy Points:
    68
    Location:
    PK
    cPanel Access Level:
    DataCenter Provider
    Have you looked at /etc/grub.conf to see if the latest kernel version is set as the default value. Sometimes you don't just need to reboot the server, but edit grub.conf manually to make sure latest kernel is set as default and then reboot.
     
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    41,494
    Likes Received:
    1,612
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    The image provided shows "Software Updates". Can you let us know the output from the command below?

    Code:
    whmapi1 system_needs_reboot
    Thank you.
     
  6. Greg M

    Greg M Member

    Joined:
    May 26, 2016
    Messages:
    20
    Likes Received:
    5
    Trophy Points:
    3
    Location:
    Glasgow, Scotland
    cPanel Access Level:
    Root Administrator
    Hi there,

    I recently had a similar issue to this, I don't use Kernel care (Although did consider it at the time and tested on a separate machine) the problem is usually that there is a kernel update that was downloaded by your server. with kernel care, it seems to be if you have installed kernel care after the new kernel is downloaded - but not activated, this means kernel care patches your current kernel while the new one remains untouched - reinstalling cPanel won't change this as the Kernel is generally updated by YUM and is not a WHM process. So while it is safe for kernel care to patch your "old" kernel. You will still have the new one in the list and your server will still think its the latest and most up to date one.

    Kernel care would then patch your current loaded kernel - this means that your server / WHM will still detect the newer kernel in the kernel list and basically wants to use it. Even though your "old" kernel is fully patched by kernel care

    Generally what you need to do is to edit your grub conf and select your current loaded kernel as the boot kernel. This should then remove the message as WHM and your server won't detect a kernel version mismatch.


    In my case, my kernel updated and I rebooted (without kernel care) the new kernel crashed the system and stuck my Dedicated server into its emergency mode. Tech guy at the DC booted to the previous kernel for me and I then had to update the grub conf to the previous kernel HOWEVER, After a reboot (I wanted to test that it was sorted) the reboot message reappeared, I noticed that the Kernel that was booted had changed its ID number, I had set it as 2 as the rescue/emergency mode was 0. This meant after the reboot, 0 became the "new" kernel which doesn't work and 1 became my stable one. So I had to change the grub conf again to book kernel ID 1. Basically, the server did boot the correct kernel but that same kernels Id the changed from 2 to 1 (I'm assuming after a succesfull reboot).



    Anyway I hope this helps shed light for those experiencing this issue.

    The following commands can be used to find and set the correct kernel, on the last one change '1' to your desired kernel from the awk command



    # awk -F\' '$1=="menuentry " {print i++ " : " $2}' /etc/grub2.cfg

    # uname -r

    # grub2-editenv list


    # grub2-set-default 1


    this article explains deeper

    HowTos/Grub2 - CentOS Wiki
     
Loading...

Share This Page