state: falha na verificação ao executar canonical-livepatch

Question

Acabei de instalar o pacote canônico de snap ao vivo:

sudo snap install canonical-livepatch
sudo canonical-livepatch enable (and the code)

Eu também configuro atualizações autônomas:

sudo apt install unattended-upgrades
sudo dpkg-reconfigure unattended-upgrades

No entanto, quando quero verificar o status do livepatch ao fazer isso:

canonical-livepatch status --verbose

Eu entendo isso:

client-version: "5"
machine-id: a144ba7b92ec478495cc5918743fe0e7
machine-token: 46a92999127246328b5091f493ee7be0
architecture: x86_64
cpu-model: Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz
last-check: 2016-11-02T11:38:33.551353308+02:00
boot-time: 2016-11-02T11:40:22+02:00
uptime: 12m0s
status:
- kernel: 4.4.0-45.66-generic
  running: true
  livepatch:
    state: check-failed
    version: ""
    fixes: ""

Devo me preocupar com a mensagem state: check-failed ? Em caso afirmativo, o que está causando isso e como posso corrigi-lo?

    

Answer 1

Sim, você deve se preocupar. Eu tenho esse problema tambem. O melhor que posso fazer é desativar e reativar o livepatching todos os dias (funciona por algumas horas e depois para).

Você pode ver o log:

# systemctl status snap.canonical-livepatch.canonical-livepatchd.service

Por algum motivo, ele para de se autenticar com o serviço após algum tempo:

● snap.canonical-livepatch.canonical-livepatchd.service - Service for snap application canonical-livepatch.canonical-livepatchd
   Loaded: loaded (/etc/systemd/system/snap.canonical-livepatch.canonical-livepatchd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2016-10-22 11:38:29 EDT; 1 weeks 3 days ago
 Main PID: 8435 (canonical-livep)
   CGroup: /system.slice/snap.canonical-livepatch.canonical-livepatchd.service
           └─8435 /snap/canonical-livepatch/15/canonical-livepatchd

Nov 02 03:39:08 firstborn canonical-livepatch[8435]: No payload available.
Nov 02 04:39:09 firstborn canonical-livepatch[8435]: Checking with livepatch service.
Nov 02 04:39:09 firstborn canonical-livepatch[8435]: Bad server status code: 403. URL: https://livepatch.canonical.com/api/machine/<id> {"error": "Invalid Machine Token"}
Nov 02 04:39:09 firstborn canonical-livepatch[8435]: No payload available.
Nov 02 05:39:09 firstborn canonical-livepatch[8435]: Checking with livepatch service.
Nov 02 05:39:09 firstborn canonical-livepatch[8435]: Bad server status code: 403. URL: https://livepatch.canonical.com/api/machine/<id> {"error": "Invalid Machine Token"}
Nov 02 05:39:09 firstborn canonical-livepatch[8435]: No payload available.
Nov 02 06:39:09 firstborn canonical-livepatch[8435]: Checking with livepatch service.
Nov 02 06:39:09 firstborn canonical-livepatch[8435]: Bad server status code: 403. URL: https://livepatch.canonical.com/api/machine/<id> {"error": "Invalid Machine Token"}
Nov 02 06:39:09 firstborn canonical-livepatch[8435]: No payload available.