Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.altnautica.com/llms.txt

Use this file to discover all available pages before exploring further.

Diagnostics

The Diagnostics page is the agent’s system-health surface: hardware utilization, temperatures, systemd unit state, and quick actions for restart and reboot.
Diagnostics page

System panel

CPU usage, core count, memory total / used / percent, disk total / used / percent, and the temperature sensors the kernel exposes (cpu_thermal, SoC, board-level). The page polls /api/system every five seconds.

Services panel

Every systemd unit in the agent’s set. Each row shows unit name, active / inactive, sub-state (running, dead, failed), and PID.

Per-service actions

ActionEffect
Restartsystemctl restart on the unit.
StopStop without disabling.
LogsFilter the Logs page to this service.

Reboot

A reboot button at the bottom of the page calls /api/v1/setup/reboot. The reboot is graceful: the agent flushes state, stops services, and schedules the reboot.

Profile gating

Shared route — visible on both profiles.

Backend endpoints

MethodPathPurpose
GET/api/systemCPU / memory / disk / temps
GET/api/servicesUnit list
POST/api/services/{name}/restartRestart a unit
POST/api/v1/setup/rebootReboot the node

Troubleshooting

The agent could not reach its own dbus connection to systemd. Run systemctl status ados-supervisor over SSH. A typical cause is a permission misconfiguration on the unit file.
Open the service’s logs from the row action. The most common causes are missing hardware (the service waits forever for a device), a config typo (the service crashes on parse), or an upstream dependency the service waits on. Restart with the dependency healthy.