How to Set Canonical Livepatch On Ubuntu 20.04 “Focal Fossa”
Canonical Livepatch was launched in Ubuntu 16.04. The livepatch possibility lets you set up kernel updates with out system reboot. It’s a nice possibility and servers should have it enabled to forestall system reboot.
The upcoming Ubuntu 20.04 “Focal Fossa” helps Canonical Livepatch.
Livepatch essential for servers
In case your server is powered by Ubuntu, then you must allow Canonical Livepatch. Livepatch will silently set up Kernel updates with out requiring a system reboot. Although it is usually availbale for Desktop customers however is much less helpful.
The whole objective of Livepatch is to forestall the system reboot after the kernel updates, the desktop customers will anyway restart the pc once in a while. So Livepatch will be put in and setup however will not often be used.
Additionally, it’s essential to notice that Livepatch characteristic is free for as much as three units for private use. You’ll be able to arrange Livepatch on Desktops, servers, digital machines, and within the cloud. Organizations might want to pay for the service by subscribing to Ubuntu Benefit.
Methods to arrange Canonical Livepatch in Ubuntu 20.04 “Focal Fossa”
For Ubuntu desktop customers
Establishing livepatch on Ubuntu desktop could be very easy. Open settings and go to Software program & updates. Go to Livepatch tab.
Ubuntu 20.04 Livepatch settings
Click on the “Check in” button and enter your Ubuntu credentials. In the event you shouldn’t have Ubuntu account, please create one.
Check in to arrange livepatch
Signal on Ubuntu Account
After signed in, click on Proceed when the popup exhibits up confirming you might be logged in.
activate Livepatching in Ubuntu 20.04
And that’s it. The livepatch is ready up in your Ubuntu 20.04 Desktop.
Errors In Ubuntu 20.04 with Livepatch
You could encounter the next error when enabling Livepatch on Ubuntu 20.04 Focal Fossa –
Didn’t allow Livepatch: can not allow machine: this machine ID is already enabled with a distinct key or is non-unique. Both “sudo canonical-livepatch disable” on the opposite machine, or regenerate a novel /and so forth/machine-id on this machine with “sudo rm /and so forth/machine-id /var/lib/dbus/machine-id && sudo systemd-machine-id-setup” server response: Conflicting machine-id
To repair the error, kind the next instructions within the terminal –
cp /and so forth/machine-id /and so forth/machine-id.unique
cp /var/lib/dbus/machine-id /var/lib/dbus/machine-id.unique
nano /and so forth/machine-id (to take away the prevailing worth)
> Initializing machine ID from D-Bus machine ID.
cat /and so forth/machine-id
For Ubuntu servers
Establishing Canonical Livepatch service is even simpler on Ubuntu servers. Head over to Ubunut’s Livepatch web page, and choose “Ubuntu consumer”. Click on “Get your livepatch token”.
Canonical Livepatch service token
It should present your livepatch token and the instructions to put in and allow livepatch service. Now copy the instructions one after the other and run on the server.
sudo snap set up canonical-livepatch
sudo canonical-livepatch allow UNIQUE_TOKEN
It’s accomplished! The livepatch arrange and put in on the server. To examine the standing, run the next command –
canonical-livepatch standing –verbose
how to install canonical livepatch,livepatch requires an internet connection,ubuntu canonical update,canonical-livepatch snap is not available,canonical livepatch pricing,gnome online accounts is required to enable livepatch,ubuntu patch management,canonical kernel update