Hi Kian,

`snap remove canonical-livepatch` seems to have fixed it.  I was able to run `pro detach` and then `pro attach` with a new token.  I think I’m all set.  Thanks.

Mike

Michael L. Metts (he/him/his)
/ˈmaɪkəɫ ˈɛɫ ˈmɛts/
Principal Data Engineer
CORNERSTONE RESEARCH
1302 El Camino Real, Suite 250
Menlo Park, CA  94025-4327
650.470.7171 direct
650.740.8551 mobile
www.cornerstone.com

From: <email address hidden> <email address hidden> On Behalf Of Kian Parvin
Sent: Thursday, June 6, 2024 8:06 AM
To: Metts, Michael <email address hidden>
Subject: [Bug 2068100] Re: ran `pro detach` to i could then run `pro attach ...` but `pro detach` failed on livepatch

EXTERNAL SENDER

Hi Michael,

Strange that there are no logs. Let's try the following instead.

First, let us know the contents of this file if it exists,

- sudo cat /var/snap/canonical-livepatch/current/livepatchd.err

At this point, if you just want to `pro detach` you can try removing the
Livepatch first.

- sudo snap remove canonical-livepatch

Then try `sudo pro detach`.

Alternatively if you want to dig deeper into the issue we can try the
following. Please provide us with the output from the following
commands,

- ps aux | grep livepatch
- sudo snap stop canonical-livepatch
- ps aux | grep livepatch

Then try run the daemon manually

- sudo SNAP_COMMON=/var/snap/canonical-livepatch/common
SNAP_DATA=/var/snap/canonical-livepatch/current /snap/canonical-
livepatch/current/canonical-livepatchd

And then in a separate terminal,

- canonical-livepatch status

Let us know the output from the above. After this you can start the
service again with

- sudo snap start canonical-livepatch

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/2068100<https://bugs.launchpad.net/bugs/2068100>

Title:
ran `pro detach` to i could then run `pro attach ...` but `pro detach`
failed on livepatch

Status in Canonical Livepatch Client:
New
Status in ubuntu-advantage-tools package in Ubuntu:
Incomplete

Bug description:
the problem is reported in /var/log/ubuntu-advantage.log but i'm not
sure how to fix it. i just want to detach and re-attached but i want
to make sure liveupdate is turned off.

root@crcoubu2:~# lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 32.3~22.04
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jun 4 23:51:39 2024
InstallationDate: Installed on 2023-03-30 (432 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: none
jobs-status.json: {"metering": {"last_run": "2024-06-05T05:47:55.559250+00:00", "next_run": "2024-06-05T09:47:55.559250+00:00"}, "update_contract_info": null, "update_messaging": {"last_run": "2024-06-05T01:01:36+00:00", "next_run": "2024-06-05T07:01:36+00:00"}}
livepatch-status.txt-error: Failed running command '/snap/bin/canonical-livepatch status' [exit(1)]. Message: error executing status: livepatchd error: daemon shutting down
uaclient.conf:
contract_url: https://contracts.canonical.com<https://contracts.canonical.com>
log_level: debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-livepatch-client/+bug/2068100/+subscriptions<https://bugs.launchpad.net/canonical-livepatch-client/+bug/2068100/+subscriptions>
"***********************************************************
Warning: This email may contain confidential or privileged information
intended only for the use of the individual or entity to whom it is
addressed. If you are not the intended recipient, please understand 
that any disclosure, copying, distribution, or use of the contents 
of this email is strictly prohibited.
***********************************************************"