• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

How do I update kernel safely?

S

sunmacet

Guest
We are having kernel panic about once a day. We would like to update kernel first before we look more options to find out what is the problem.

Command "yum update kernel" gives newer kernel but is kernel update safe? This is production server and major downtime is not an option. Also we don't have access to console, so if boot fails we need to call to our server provider that might take too long time.

Is there any means to be safe with kernel update? Is there ways to setup GRUP so that it will use older kernel if the newer fails? Any other means to make the kernel update more safe? In generally is these yum kernel updates safe? Any other thought?

Thank you for your time.
 
Thank you. It seems to be exactly what I was looking for. I will make the kernel update when I get the courage. :)

I have some very bad memories about kernel update from about 7 years ago that still haunts me. ;)
 
that should do it then. If the kernel doesnt boot for some reason, which is what that page is all about, it will automatically reboot into whatever other kernel you defined as default.
 
also you should try to use yum install kernel instead of yum update as the update will remove the previous version but install will keep them all.
 
oh man good point. Never use rpm -U with a kernel, always use rpm -i. Thats what yum install does too, the difference is that -U is an upgrade of the existing package, and -i (with kernels ONLY) will install an addition kernel, rather than replace the existing one.
 
oh, i did use yum update... :(

however it seems that /boot has the old vmlinuz and initrd, does it mean that I am safe? haven't rebooted yet...
 
AFAIK yum update doesn't remove all your old kernels (see installonlypkgs in /etc/yum.conf). rpm -U does.

however it seems that /boot has the old vmlinuz and initrd, does it mean that I am safe? haven't rebooted yet...

See what's in /etc/grub.conf.
 
Back
Top