Livepatch enable not found?












2















machine is running Xenial, updated from Wily using do-dist-upgrade



Trying to set up live patching as an experiment before apply to my seedbox (a different machine)



Following these instructions
cyberciti.biz/faq/howto-live-patch-ubuntu-linux-server-kernel-without-rebooting/



~$ canonical-livepatch status
Machine is not enabled. Please run 'sudo canonical-livepatch enable' with the
token obtained from https://ubuntu.com/livepatch.

~$ sudo canonical-livepatch enable [key]
sudo: canonical-livepatch: command not found


Please advise.










share|improve this question























  • That's odd. Does sudo $(which canonical-livepatch) enable [key] work?

    – Chai T. Rex
    Nov 16 '16 at 1:10











  • Is the canonical-livepatch snap installed properly and working? snap list will show you the installed snaps and you can verify that the service is running by systemctl status snap.canonical-livepatch.canonical-livepatchd.service

    – Manik Taneja
    Nov 16 '16 at 2:13
















2















machine is running Xenial, updated from Wily using do-dist-upgrade



Trying to set up live patching as an experiment before apply to my seedbox (a different machine)



Following these instructions
cyberciti.biz/faq/howto-live-patch-ubuntu-linux-server-kernel-without-rebooting/



~$ canonical-livepatch status
Machine is not enabled. Please run 'sudo canonical-livepatch enable' with the
token obtained from https://ubuntu.com/livepatch.

~$ sudo canonical-livepatch enable [key]
sudo: canonical-livepatch: command not found


Please advise.










share|improve this question























  • That's odd. Does sudo $(which canonical-livepatch) enable [key] work?

    – Chai T. Rex
    Nov 16 '16 at 1:10











  • Is the canonical-livepatch snap installed properly and working? snap list will show you the installed snaps and you can verify that the service is running by systemctl status snap.canonical-livepatch.canonical-livepatchd.service

    – Manik Taneja
    Nov 16 '16 at 2:13














2












2








2








machine is running Xenial, updated from Wily using do-dist-upgrade



Trying to set up live patching as an experiment before apply to my seedbox (a different machine)



Following these instructions
cyberciti.biz/faq/howto-live-patch-ubuntu-linux-server-kernel-without-rebooting/



~$ canonical-livepatch status
Machine is not enabled. Please run 'sudo canonical-livepatch enable' with the
token obtained from https://ubuntu.com/livepatch.

~$ sudo canonical-livepatch enable [key]
sudo: canonical-livepatch: command not found


Please advise.










share|improve this question














machine is running Xenial, updated from Wily using do-dist-upgrade



Trying to set up live patching as an experiment before apply to my seedbox (a different machine)



Following these instructions
cyberciti.biz/faq/howto-live-patch-ubuntu-linux-server-kernel-without-rebooting/



~$ canonical-livepatch status
Machine is not enabled. Please run 'sudo canonical-livepatch enable' with the
token obtained from https://ubuntu.com/livepatch.

~$ sudo canonical-livepatch enable [key]
sudo: canonical-livepatch: command not found


Please advise.







16.04 ubuntu-core canonical-livepatch






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '16 at 1:07









SilvestrisSilvestris

598




598













  • That's odd. Does sudo $(which canonical-livepatch) enable [key] work?

    – Chai T. Rex
    Nov 16 '16 at 1:10











  • Is the canonical-livepatch snap installed properly and working? snap list will show you the installed snaps and you can verify that the service is running by systemctl status snap.canonical-livepatch.canonical-livepatchd.service

    – Manik Taneja
    Nov 16 '16 at 2:13



















  • That's odd. Does sudo $(which canonical-livepatch) enable [key] work?

    – Chai T. Rex
    Nov 16 '16 at 1:10











  • Is the canonical-livepatch snap installed properly and working? snap list will show you the installed snaps and you can verify that the service is running by systemctl status snap.canonical-livepatch.canonical-livepatchd.service

    – Manik Taneja
    Nov 16 '16 at 2:13

















That's odd. Does sudo $(which canonical-livepatch) enable [key] work?

– Chai T. Rex
Nov 16 '16 at 1:10





That's odd. Does sudo $(which canonical-livepatch) enable [key] work?

– Chai T. Rex
Nov 16 '16 at 1:10













Is the canonical-livepatch snap installed properly and working? snap list will show you the installed snaps and you can verify that the service is running by systemctl status snap.canonical-livepatch.canonical-livepatchd.service

– Manik Taneja
Nov 16 '16 at 2:13





Is the canonical-livepatch snap installed properly and working? snap list will show you the installed snaps and you can verify that the service is running by systemctl status snap.canonical-livepatch.canonical-livepatchd.service

– Manik Taneja
Nov 16 '16 at 2:13










1 Answer
1






active

oldest

votes


















3














I did have the same error message, log files did not help me either.
So I did as root:



snap remove canonical-livepatch
apt update && apt upgrade && apt dist-upgrade
reboot


afterwards again as root:



sudo snap install canonical-livepatch 
sudo canonical-livepatch enable **your token here**


output was: Successfully enabled device. Using machine-token: your token here
:)






share|improve this answer
























  • Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

    – Silvestris
    Jan 21 '17 at 18:35











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f849904%2flivepatch-enable-not-found%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














I did have the same error message, log files did not help me either.
So I did as root:



snap remove canonical-livepatch
apt update && apt upgrade && apt dist-upgrade
reboot


afterwards again as root:



sudo snap install canonical-livepatch 
sudo canonical-livepatch enable **your token here**


output was: Successfully enabled device. Using machine-token: your token here
:)






share|improve this answer
























  • Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

    – Silvestris
    Jan 21 '17 at 18:35
















3














I did have the same error message, log files did not help me either.
So I did as root:



snap remove canonical-livepatch
apt update && apt upgrade && apt dist-upgrade
reboot


afterwards again as root:



sudo snap install canonical-livepatch 
sudo canonical-livepatch enable **your token here**


output was: Successfully enabled device. Using machine-token: your token here
:)






share|improve this answer
























  • Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

    – Silvestris
    Jan 21 '17 at 18:35














3












3








3







I did have the same error message, log files did not help me either.
So I did as root:



snap remove canonical-livepatch
apt update && apt upgrade && apt dist-upgrade
reboot


afterwards again as root:



sudo snap install canonical-livepatch 
sudo canonical-livepatch enable **your token here**


output was: Successfully enabled device. Using machine-token: your token here
:)






share|improve this answer













I did have the same error message, log files did not help me either.
So I did as root:



snap remove canonical-livepatch
apt update && apt upgrade && apt dist-upgrade
reboot


afterwards again as root:



sudo snap install canonical-livepatch 
sudo canonical-livepatch enable **your token here**


output was: Successfully enabled device. Using machine-token: your token here
:)







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 '16 at 22:18









martendmartend

554




554













  • Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

    – Silvestris
    Jan 21 '17 at 18:35



















  • Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

    – Silvestris
    Jan 21 '17 at 18:35

















Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

– Silvestris
Jan 21 '17 at 18:35





Yeah, same thing worked here- basically just wiping it and starting over. No idea why it worked the second time but not the first. I guess "uninstall and try again" is the software equivalent of "try restarting it" lol

– Silvestris
Jan 21 '17 at 18:35


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f849904%2flivepatch-enable-not-found%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Questions related to Moebius Transform of Characteristic Function of the Primes

List of scandals in India

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?