With previous Ubuntu releases, yes, we did use Livepatch and, as you have experienced, had no issues or problems. However, from Ubuntu 24.04 LTS onward, we've invoked more and more customization, so we disabled Livepatch, to fall in line with our policy of manual upgrades only, on everything (including Plesk).
@learning_curve and
@AlL,
One thing to note is this.
There is KernelCare and Canonical LivePatch ............ and, as usual, they are - allegedly - not working properly when installed on the same system.
Normally, one would recommend to
a) use Ubuntu "native" code and packages, like LivePatch, and
b) ignore the - often mistaken - allegations of CloudLinux / Imunify / TuxCare that concern the lack of compatibilit.
However, in the case of KernelCare vs Canonical LivePatch, it is - best - to not ignore the warnings regarding conflicts between KernelCare and LivePatch.
KernelCare and LivePatch work in different ways, so there is added value for both.
Nevertheless, combining them continuously on one server is not recommended.
A good rule of thumb is this :
1 - check whether you have a valid license for Imunify :
1.1 run command : imunify360-agent rstatus ( if you have a license, then output should be : OK )
1.2 run command : kcarectl --license-info ( if you have a license with Imunify, then output should be : Key-based valid license found )
2 - check whether you have Livepatch enabled with Ubuntu Pro - run command : pro status ( livepatch status is by default : enabled )
3 - make sure that you are at latest (safe) kernel : use Livepatch to do so, with apt commands and a reboot afterwards
4 - disable Livepatch - run command : pro disable livepatch ( if required, run command pro status again to check )
5 - keep track of KernelCare activity - for instance, by means of :
5.1 - run command : kcarectl --patch-info
5.2 - run command : kcarectl --uname ( shows effective kernel)
5.3 - run command : cat /proc/kcare/cvelist
5.4 - if necessary, run command : cat /etc/sysconfig/kcare/kcare.conf ( with AUTO_UPDATE=True, KernelCare is active - alternate value "False" disables the automatic updates, including cron-based patches )
6 - whenever needed ( and this is the case with highly severe CVE ), again update to the latest (safe) kernel with Canonical Livepatch ( enable it first! )
and that way, one has the advantages of KernelCare (bootless kernel and lib updates) and Livepatch (highly critical kernel updates).
Hope the above helps a bit.
Kind regards....