Symptoms
WHM presents the following banner that doesn't seem to be cleared upon reboot:
Description
This issue occurs when the kernel has recently been updated but the server has not been updated. You can use the following WHMAPI function to check if the system reboot is required:
whmapi1 system_needs_reboot
Workaround
1. You will first want to confirm the running kernel version using the following command:
uname -r
If you're seeing the updated kernel is running, you will then need to review your GRUB configuration for the kernel boot version using the following commands:
awk -F\' '$1=="menuentry " {print i++ " = "$2}' /etc/grub2.cfg
grub2-editenv list
You will then want to ensure that you set the updated kernel to boot:
grub2-set-default 0
Next, you will want to make a backup if the existing GRUB configuration:
cp -vi /boot/grub2/grub.cfg{,.bak}
Once a backup has been made, you will then need to rebuild the GRUB configuration:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
2. Your server time may not be properly updated or synchronized. The system's clock can cause the system to not be able to properly identify that a reboot has occurred as the current system time may be behind the updated package timestamp. You will want to ensure that the system time is updated using the following commands:
date
Using the time presented in the output from the command above, you can then check for when the package was last updated by grepping the package's installation information from the yum.log file:
grep $package /var/log/yum.log
*NOTE: You will want to replace $package with the package name reported from the system_needs_reboot API call output.
You can also ensure that your server time is in sync by using NTP.
If you are not seeing the updated kernel version in your GRUB configuration, or that your server time is out of date, you will want to work with your system administrator for further diagnosis and troubleshooting. If you do not have a system administrator, you may be able to find one in our listings here: