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
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