Troubleshooting helps you find and fix the most common problems on a Binions host — from a package that won't install to a daemon that won't start, a stuck playbook, or a slow workflow.
Almost every problem starts the same way: ask the platform what it thinks is wrong. Three commands answer that for any daemon — a readiness roll-up, the systemd state, and the recent logs — and most pages in this section build on them.
Start here. Run these first; they point you at the right page below.
binions-cliconsole status # every daemon's readiness, in one table
systemctl status binions-<name> # one daemon's systemd state
journalctl -u binions-<name> -n 100 --no-pager # its recent logs
Naming reminder. systemd units are
binions-<name>(for examplebinions-playbook), not<name>-service.binions-cliconsoleis a command-line tool, not a service.