This procedure requests KernelCare kernel live patches on a server you are authorized to administer. It is not a WordPress update or an update of every operating-system package. Hosting-account users should ask the server administrator to perform it.
Before applying patches
Record the running kernel with uname -r, the architecture with uname -m, and the current patch report. Confirm coverage for that exact kernel, a working licence and access to the configured patch source. Keep a separate administrative connection available and agree on a maintenance window appropriate to the server.
If an existing incident is under investigation, preserve its logs and current state first. Do not add force options or change update policies simply to make the command succeed.
Request the update
In an authorized root shell, run the manual update command documented by TuxCare:
/usr/bin/kcarectl --updateThe words “as root” describe the required account. They are not command arguments. Read the full response and keep any error text with the time of the attempt.
Verify the result
Inspect the patch information after the command:
/usr/bin/kcarectl --info
/usr/bin/kcarectl --patch-infoCompare the result with the expected patches for the running kernel. An installed agent or an unchanged uname -r string alone does not establish whether a particular CVE is fixed. The cPanel KernelCare reference distinguishes checking applied patches from requesting an update.
Check the applications and monitoring relevant to this server. Record what changed and any outstanding maintenance. Live patching does not establish that all software on the machine is current.
If the update fails
Keep the exact error, kernel version, agent version and patch report. TuxCare documents cases where an HTTP 401 error can accompany a zero exit status; a shell success code alone is insufficient evidence.
Ask the responsible administrator to investigate licence, connectivity or kernel-support issues before retrying. A patch removal or reboot is a separate maintenance decision, not a generic response to an unclear result. Contact Nuagerie support with sanitized output; omit licence keys and credentials.