You have just installed Binions — this short checklist confirms your set is healthy and ready to build on. Run through it once after a fresh install (or after adding a new daemon): check that the services are running, their health endpoints answer, the logs look clean, the licence is in force, and the installed versions are what you expect. Every step is a command you can copy and paste.
Five quick checks. Services running → health endpoints pass → logs clean → licence active → versions correct. If all five pass, your host is ready. If any fail, each step points you at the right place to look.
The examples below use the logger daemon, because it is the simplest service and the one you most likely installed first. For any other daemon, swap logger for its name (for example mailbox or scheduler) and use that daemon’s health port from the table in step 2.
Every Binions daemon runs as two systemd units: the daemon itself, binions-<service>, and its bundled private event bus, redis-binions-<service>. Both should be active. Check the daemon you installed:
systemctl is-active binions-logger redis-binions-loggerYou should see active printed twice — once for the daemon, once for its Redis. To check every Binions service on the host at once, use the wildcard form:
systemctl is-active 'binions-*.service' 'redis-binions-*.service'This prints one line per unit. Every line should read active. Anything reading inactive or failed needs attention — see Install problems.
Each daemon exposes a health endpoint on the loopback address 127.0.0.1, on its own port in the 91xx range. A successful /health/ready response means the daemon is up and its event bus is reachable. Check the logger:
curl -sf http://127.0.0.1:9100/health/ready && echo OKYou should see OK. (The -f flag makes curl stay silent and fail if the endpoint returns an error, so a bare OK is your all-clear.) Each daemon also offers /health/live, which reports only whether the process itself is alive. Use the port for whichever daemon you are checking:
| Daemon | Health port |
|---|---|
| binions-logger | 9100 |
| binions-database | 9102 |
| binions-traefiklinker | 9103 |
| binions-aiinjector | 9104 |
| binions-datatransporter | 9105 |
| binions-dataanaliser | 9106 |
| binions-mailbox | 9107 |
| binions-playbook | 9108 |
| binions-webhookcaller | 9109 |
| binions-scheduler | 9110 |
| binions-showman | 9111 |
| binions-modbus | 9112 |
For example, to check the mailbox daemon you would run curl -sf http://127.0.0.1:9107/health/ready && echo OK. If a health check returns 503 instead of OK, the daemon is running but cannot reach its event bus — head to Install problems.
A healthy daemon writes its events to the system journal. Read the last 20 lines for the daemon you installed:
journalctl -u binions-logger -n 20 --no-pagerOn a clean start you should see the daemon report that it has started, connected to its Redis event bus, and is ready — with no repeating errors or restart loops. To watch a window of recent activity instead, scope it by time:
journalctl -u binions-logger --since "10 minutes ago" --no-pagerIf the logs are noisy. Repeated connection errors usually point at the daemon’s Redis or, for daemons that reach beyond the host, a missing external dependency — for example database credentials for
binions-databaseor an API key forbinions-aiinjector. For how to read the journal and what common messages mean, see Logs.
Each daemon checks its licence at boot. This makes your earlier checks do double duty: if a daemon is running and its health endpoint returns OK, its licence has already been accepted. There is no separate licence command to run here — a healthy daemon is a licensed daemon.
Each daemon’s licence lives at /etc/binions/<daemon>.license. If a daemon fails to start specifically because of its licence — for instance after moving to a paid set or a new host — the journal from step 3 will say so. In that case, work through Activating a licence to put the right licence in place.
Free tier reminder. One set on one host is free for non-commercial use. Commercial use, or a second host, needs a paid licence. If a daemon is healthy, you are already covered for that set — details are in Activating a licence.
Finally, confirm which versions are installed — useful for support, for reproducing a setup on another host, or before and after an upgrade. List every Binions package and its version:
dpkg -l 'binions-*'The version column should show the release you intended to install, and the status column (ii) should show each package is properly installed. If you pinned a version with apt-mark hold during installation, this is where you confirm the hold is in effect.
If any check above did not pass, you do not need to guess. Start from the symptom:
inactive or failed, or a health check does not return OK — read the daemon’s journal (step 3) for the reason, then see Install problems for fixes to the most common install and startup issues.binions-database, binions-mailbox, and binions-aiinjector need a database, mail credentials, or an API key before they will become healthy. The Installation guide covers each one.Check the logs first. Almost every failed check has a one-line explanation waiting in the daemon’s journal. Run
journalctl -u binions-<service> -n 50 --no-pagerbefore changing anything — the message there tells you whether it is a configuration, dependency, or licence problem, and saves you guessing.
With your set confirmed healthy, you are ready to put it to work: