Comment 1 for bug 2039030

Hi,

Thanks for the report. It's likely not the case that the get-resource-token action needs to be run again. A few things,

- You can try `juju run-action livepatch/<unit> restart` to restart the server and see if that addresses the issue. In any case though the charm should be starting the server when the machine is restarted so that still needs some investigating.
- Looking at the logs from `juju debug-log` and inside the machine via `juju ssh livepatch/leader` then `journalctl` is there anything indicating why Livepatch can't/was unable to start after the machine was rebooted?
- The charm revision seems out of date, the latest revision in "latest/stable" is "39" as seen here https://charmhub.io/canonical-livepatch-server