Can't enable or disable livepatch.

[Robin Huber]

I cannot use livepatch and I don't know why. I tried to completely purge the snap but it always results in the cryptic error

connection to the daemon failed: Get "http://127.0.0.1/enable": dial unix /var/snap/canonical-livepatch/278/livepatchd.sock: connect: no such file or directory

Content of lsb_release -rb:

Description: Ubuntu 22.04.4 LTS
Release: 22.04

Canonical-livepatch is a snap, and as such I cannot provide apt-cache policy

Output of uname -a:

Linux loyaltymc 6.5.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 31.2.3~22.04
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Apr 21 15:26:59 2024
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:

cloud-id.txt-error: Invalid command specified 'cloud-id'.
livepatch-status.txt-error: Failed running command '/snap/bin/canonical-livepatch status' [exit(1)]. Message: connection to the daemon failed: Get "http://127.0.0.1/status?format=yaml&verbosity=2": dial unix /var/snap/canonical-livepatch/278/livepatchd.sock: connect: no such file or directory
pro-journal.txt: -- No entries --
uaclient.conf:
 contract_url: https://contracts.canonical.com
 log_level: debug

[Grant Orndorff (orndorffgrant)]

Hello theroblp!

Thank you for the bug report! I'm assigning this bug to the livepatch snap as this seems to be a bug in the snap package.

It looks like even `snap install canonical-livepatch` is failing.

I'll leave it as "incomplete" for the ubuntu-pro-client (ubuntu-advantage-tools) for now in case it turns out to be a bug there.

[Kian Parvin (kian-parvin)]

Hi Robin,

Could you please uninstall the snap with `sudo snap remove canonical-livepatch` then re-install it with `sudo snap install canonical-livepatch` and then provide us with the output from the following commands to investigate further.

- snap info canonical-livepatch
- canonical-livepatch status --verbose
- journalctl -t canonical-livepatch.canonical-livepatchd
- snap connections canonical-livepatch
- ls -la /var/snap/canonical-livepatch/current

The Livepatch snap is made up of a daemon and a client, the daemon is always running in the background and when you run a command like `canonical-livepatch status` the client sends a request over a unix socket located at /var/snap/canonical-livepatch/current/livepatchd.sock or /var/snap/canonical-livepatch/current/livepatchd-priv.sock to the daemon. On your system it looks like the socket is never created.