• 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.

Input Reboot required after kernel update

Redsector

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.51 Update #1
Today I found out that my VPS needed a reboot due to kernel update.
Plesk was not aware of that.

I've now added a script to check file "/var/run/reboot-required" to alert me whenever is necessary.

I suppose this feature should be implemented in Plesk natively to either reboot automatically (bad idea) or to alert via email a reboot may be necessary.
 
It is quite unusual that a Kernel update is done "automatically". It cannot be expected that application layers watch that as updating the Kernel itself requires administrator attention. It is also clear that unless you are using KernelCare that allows using updated Kernels without reboot a reboot is required under Linux, because the Kernel is the - well - kernel of things. I suggest that you try to find out why Kernel update occurred without you knowing about it. Maybe ask the data center if they "manage" the server for you?
 
In debian, plesk doesn't even show kernel upgrades as they require a dist-upgrade.
In ubuntu, a kernel update might be done automatically by ubuntu itself if it is tagged as a security update.
 
Back
Top