I'm got two dedicated servers with WHM set up. Server software is very similar on both, and both are up-to-date with WHM. One of them has had a few quirks lately, the latest of which is a required reboot for kernel upgrade. We had been managing kernel upgrades with Ksplice and haven't updated the running kernel since that went away.
Following the WHM 64 update, I installed KernelCare on one of the servers using the Ksplice to KernelCare migration script. Appeared to go fine, and Security Center sees it and says we're on kernel 2.6.32-673.26. However, I'm still getting the alert in the top right saying "You must reboot the kernel to update kernel." I checked uname -a on the shell, and sure enough I'm getting an older version: 2.6.32-531.17.
What's needed to get the proper kernel running? Is there a way to avoid a reboot? And why is Security Center reporting a different version than uname?
Following the WHM 64 update, I installed KernelCare on one of the servers using the Ksplice to KernelCare migration script. Appeared to go fine, and Security Center sees it and says we're on kernel 2.6.32-673.26. However, I'm still getting the alert in the top right saying "You must reboot the kernel to update kernel." I checked uname -a on the shell, and sure enough I'm getting an older version: 2.6.32-531.17.
What's needed to get the proper kernel running? Is there a way to avoid a reboot? And why is Security Center reporting a different version than uname?