Troubleshooting

The system doesn’t start after an update

Restart and choose the previous entry in the boot menu. If the menu doesn’t appear, hold Shift (or press Esc) while the computer starts. Once you are in, make the previous deployment the default:

sudo bootc rollback

Then report the problem, so the next update can fix it.

Something broke after an update

Roll back the same way, and check whether the problem goes away. Say so in your report: it tells us the update caused it.

An agent isn’t recognised

Check that the agent service is running:

systemctl status agentd
agentctl ps

A program only becomes an AI agent once it calls a model through the gateway. If it uses its own key and endpoint, see Programs that bring their own key.

Model calls fail

• Check that at least one source is set up in Model Gateway, and that its key is valid.
• Check whether the agent has reached its quota (agenttop).
• For a local model, check that its server is running.

The desktop feels slow

Run agenttop and look at which agents use the most CPU, memory and I/O, and which scheduling policy is in use. If a misbehaving scheduling policy is to blame, the system falls back to the default on its own; mention it in your report.

Collect information for a report

sudo bootc status > kleinia-report.txt
uname -r >> kleinia-report.txt
journalctl -b -p warning --no-pager >> kleinia-report.txt

Look through the file before sharing it, and remove anything private: API keys, host names, paths that contain names.