Troubleshooting
What to do when lnk secret refuses a grant, leaves a copy behind, or
can't reach its keeper (Secrets).
A secret is refused for an agent
Told ... is granted to main plain, and an agent is given a secret sealed only, create it again with --internet-host <its host>, then give it to the agent with lnk secret add. Told main is on aws-1: a secret is granted to it there, run lnk box ssh aws-1, then
lnk secret create and lnk secret add there.
An agent's keys are asked for again
Told main's keys are kept with your secrets now ..., give each again
as the message says (lnk agent start, lnk agent connect).
A copy stays behind
Told AGENT_MAIN_MODEL_KEY is left on aws-1: ..., the box was stopped
or offline: start it (lnk box start aws-1), then run lnk secret remove AGENT_MAIN_MODEL_KEY again. Told ... on cloud-1: removed with the agent there, remove the agent there (lnk agent delete), or move
it away from there.
The keeper doesn't answer
Told your secrets' keeper isn't answering at /run/lnk-secrets/keeper.sock, its service is stopped: sudo systemctl start lnk-secrets, and journalctl -u lnk-secrets says why it
stopped.
Two stores of your secrets
Told your secrets' keeper already keeps secrets of yours, and so does ..., your own file came back beside the keeper's: create each of its
secrets again with lnk secret create, then remove the file.
No systemd
Told the keeper runs as a service of systemd, which this machine doesn't run, your secrets stay in your own file, mode 600, which any
program you run outside a sandbox can read.