By Sonic D
#uname -r 2.6.32-504.12.2.el6.x86_64
kernel-2.6.32-504.12.2.el6.x86_64 kernel-2.6.32-642.3.1.el6.x86_64 kernel-2.6.32-642.4.2.el6.x86_64 kernel-2.6.32-642.6.1.el6.x86_64 kernel-firmware-2.6.32-642.6.2.el6.noarch kernel-headers-2.6.32-642.6.2.el6.x86_64 kernel-2.6.32-642.6.2.el6.x86_64 dracut-kernel-004-409.el6_8.2.noarch
yum update is working everyday. According to log, new kernel has been already installed. but after reboot, my OS still use 2.6.32-504.12.2.
Is there anything I can do? Does it mean that server isn’t compatible with new kernel?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
Did you switched to internally managed kernel? If not, this could make a problem, as for older Droplet, it was managed from Control Panel. Look at tutorial and if this is the case, follow it and try to update again.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.