Diagnostic commands

Curated commands for AtomOS operators. Linux generic tools apply on any well-administered host; AtomOS-specific entries come from atomos-cli as mapped in Install & CLI reference.

libvirt and hand edits

AtomOS owns guest lifecycle through its services and APIs. Avoid ad-hoc virsh define/edit or manual XML changes unless your runbook explicitly allows break-glass use — conflicting changes can desync Electros state from the host.

AtomOS-specific (atomos-cli)

Run authoritative help on the installed build:

atomos-cli --help

Command	Purpose
sudo atomos-cli --status	AtomOS service status
sudo atomos-cli --logs	Installation / service logs (-rl alias in reference)
sudo atomos-cli --info	Host and AtomOS information
sudo atomos-cli --healthcheck	Resource health check
sudo atomos-cli --pci-list	PCI devices and drivers (passthrough planning)
sudo atomos-cli --show-fingerprint	TLS certificate fingerprint for Electros trust
sudo atomos-cli --fw-info	FirewallD configuration summary
sudo atomos-cli --verify-install	Post-install verification
sudo atomos-cli --verify-network	Default route / connectivity sanity (especially cloud)
sudo atomos-cli --journal SERVICE TIME	Journal slice for an AtomOS service
sudo atomos-cli --version	Installed package versions

Service control examples:

sudo atomos-cli --restart storage
sudo atomos-cli --restart compute
sudo atomos-cli -ra

Storage and vaults:

sudo atomos-cli --vault-creator
sudo atomos-cli --vault-editor
sudo atomos-cli --volume-info

Network and trust:

sudo atomos-cli --bridge-setup
sudo atomos-cli --generate-cert
sudo atomos-cli --get-certificate 10.0.0.11 compute

Linux generic — systemd and logs

Command	Use
systemctl status UNIT	Unit state
systemctl list-units --type=service --state=running	Running services
journalctl -u UNIT -b	Boot-scoped journal for a unit
journalctl -p err -b	Errors since boot
dmesg -T | tail	Recent kernel messages

Prefer atomos-cli --journal when documenting AtomOS service names to your support team.

Linux generic — networking

Command	Use
ip addr / ip link / ip route	Addresses, links, routing
nmcli device status	NetworkManager view
nmcli connection show	Connection profiles (bridges, VLANs)
ss -tulpn	Listening sockets
curl -vkI https://127.0.0.1:7701/	Local HTTPS probe (port from install reference; path may vary)

See Networking & certificates and VLANs.

Linux generic — storage

Command	Use
lsblk -f	Block devices and filesystems
df -h /mnt	Vault mount space
mount | grep /mnt	Active vault mounts

Vault logic remains in AtomOS storage services — use atomos-cli for configuration changes.

Linux generic — virtualization inspection

Command	Use
sudo virsh list --all	Domain list (read-only troubleshooting)
sudo virsh dominfo NAME	Domain metadata
lspci -nnk	PCI IDs and drivers (compare with --pci-list)

Use read-only virsh where possible; lifecycle changes belong in Electros/GUI.

Storage API localhost (advanced)

Documented import endpoints bind to 127.0.0.1:27777 in Migration & import. Remote authentication and transport for port 27777 are not verified in this docs revision — treat off-host access as requires verification.

Example local probe (no body):

curl -sS -o /dev/null -w '%{http_code}\n' http://127.0.0.1:27777/ || true

Interpret HTTP codes in context; a connection refusal indicates storage client not listening.

Suggested triage order

flowchart TD
  A[Symptom] --> B[atomos-cli --status]
  B --> C[atomos-cli --healthcheck]
  C --> D[atomos-cli --logs / --journal]
  D --> E{Network?}
  E -->|yes| F[ip / nmcli / --verify-network]
  E -->|no| G{Storage?}
  G -->|yes| H[lsblk / df / --volume-info]
  G -->|no| I[virsh list / --pci-list]

Related pages

• Troubleshooting runbooks
• Install & CLI reference
• Quick start