• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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