If you use Ubuntu Server in your info centre, you can just take benefit of Canonical’s Livepatch service to patch the managing kernel on these servers devoid of having to reboot. This is an amazing resource that can save you from a sizeable headache, or having to appear into function immediately after hrs just to patch the kernel and reboot the procedure.
By creating use of the Canonical Livepatch service, you can ensure your systems:
- Improve service availability
- Retain protection and compliance
- Will not likely interrupt in-memory databases or other products and services
Do be aware: This is not the similar as upgrading a managing kernel. If you upgrade a managing kernel, you even now have to reboot the procedure to make the improvements just take impact. Livepatching only is effective when implementing patches to the managing kernel (such as for protection vulnerabilities).
The Livepatch service is absolutely free to use, up to three systems, and can only be used on 64-bit variations of Ubuntu 16.04 and 14.04, managing at least kernel 4.4.
If you happen to be uncertain which kernel you happen to be managing, difficulty the command uname -r to see (Determine A).
Let’s get this up and managing.
Downloading your livepatch token
The very first issue you should do is download a livepatch token from the Livepatch Support site. To use the absolutely free edition, make sure to check out Ubuntu Consumer and then simply click Get your Livepatch token. You will then be prompted to log into your UbuntuOne account. Once you’ve authenticated with your account, you will be presented with your Livepatch token (which you need to copy and save) and the necessary instructions to set up both equally Livepatch and your Livepatch token. The instructions are:
sudo snap set up canonical-livepatch sudo canonical-livepatch enable TOKEN
Where TOKEN is your actual Livepatch token.
Right after managing the 2nd command, you need to see Productively enabled machine. Utilizing matching token TOKEN (wherever TOKEN is your actual Livepatch token).
And that’s all there is to it. You can now patch your managing kernel devoid of having to reboot your procedure. Do remember, if you upgrade the kernel, the server will even now have to be rebooted. If you happen to be only patching and you have enabled the Livepatching service, your kernel will be excellent to go even devoid of a reboot.