Find answers to your questions

Documentation

Do I have to restart my server after installing KernelCare?

Not necessarily. KernelCare can apply available security patches for a supported kernel while the server is running. This does not mean the server will never need another reboot, or that installing the agent is enough to confirm its protection.

What live patching provides

The patch acts on the running kernel. It can reduce interruptions needed to apply covered fixes while leaving other maintenance for the administrator to plan. TuxCare explains that KernelCare does not replace kernel feature updates or fixes outside its scope.

After installation, have the running kernel, its support status and applied patches checked. Our KernelCare verification guide distinguishes these checks. Long uptime or the absence of a warning does not establish that every required update is active.

When a reboot may still be needed

  • A new kernel must become the running kernel, or a specific update explicitly requires a reboot.
  • Establishing the trust needed for KernelCare modules with Secure Boot can require a planned reboot. Follow the current module-signing procedure appropriate to the platform; do not disable Secure Boot by default.
  • Components outside the kernel may still need a service restart or system reboot after an update. cPanel’s explanation describes why live patching does not replace maintenance of the rest of the server.

Prepare and verify the maintenance

The administrator should identify the reason for rebooting, affected services, recovery access and expected checks. On a managed server, coordinate with support before starting a reboot. Access to your cPanel account does not mean that you administer the operating system.

After maintenance, verify the services your business uses, any errors and KernelCare’s status on the kernel now running. Retain the observations needed for follow-up without sharing passwords or license keys.

To clarify whether your service needs maintenance, contact Nuagerie with the warning you saw and its time. Our team can help identify the next step and, where relevant, plan the management of your infrastructure.

Related Articles

How to Force the Update of KernelCare In order to force the update of KernelCare you just have to use the command kcarectl --update as root An example of what it should look like: # kcarectl --update Kernel is safe For help with a Nuagerie service, open or follow up on a support request in your Client Area. For general questions, use our contact form. Does KernelCare work with third-party drivers? The CloudLinux team is devoted to making their clients lives as easy as possible, therefore KernelCare is able to work with third-party drivers. However, you will have to update the drivers manually as KernelCare does not update them. For help with a Nuagerie service, open or follow up on a support request in your... KernelCare: manage a temporary pause in automatic updates Pausing KernelCare automatic updates can be part of a documented maintenance intervention. It also leaves new patches pending, so the pause needs an owner, a deadline and a verified return to normal operation. It should not be used simply to make an error message disappear. This guide is for the server’s authorized... How to Uninstall KernelCare You can uninstall KernelCare by using the following command: # yum remove kernelcare For help with a Nuagerie service, open or follow up on a support request in your Client Area. For general questions, use our contact form. Where can I get documentation or support? For help with a Nuagerie service, open or follow up on a support request in your Client Area. For general questions, use our contact form. You can also contact KernelCare official support by emailing [email protected]. You can find KernelCare's documentation at http://docs.kernelcare.com