Most install problems come down to one of four things: a stale package index, the wrong CPU architecture, an expired repository token, or a daemon that installed cleanly but did not start. This page walks each symptom from what you see, to the likely cause, to the command that fixes it. Whenever a daemon is involved, your first move is always the same — ask Binions how it is doing with binions-cliconsole status.
The three commands you will reach for most. A readiness roll-up, one daemon’s systemd state, and its recent logs — in that order.
binions-cliconsole status # one table: every daemon's readiness (UP/DEGRADED/DOWN)
systemctl status binions-<name> # one daemon's systemd state
journalctl -u binions-<name> -n 100 --no-pager # its recent logsA quick reminder on naming: the systemd unit is binions-<name> (for example binions-logger), not <name>-service. And binions-cliconsole is a command-line tool you run on demand, not a background service.
Symptom. An apt install fails, or a daemon you expected is simply not present.
Likely cause. Your local package index is out of date, so apt cannot find the package or one of its dependencies.
Fix. Refresh the index, then re-run the install. If apt still cannot resolve the package, ask it what it knows about that package:
sudo apt update
sudo apt install binions-<name>
apt-cache policy binions-<name> # is the package visible, and from the Binions repository?apt-cache policy tells you whether the package is reachable at all and which repository would provide it. If it shows nothing, the Binions repository is not configured on this host — re-add it using the install command from your portal (see below).
Symptom. The package will not install on your machine even though apt can see the repository, or it complains the package is for a different architecture.
Likely cause. You are installing on hardware that the current alpha does not build for. The alpha packages are 64-bit x86 (amd64) only. Installing them on a Raspberry Pi or other 64-bit ARM board will fail.*
Fix. Install Binions on an amd64 host for now. Support for Raspberry Pi and other ARM hardware arrives with the public 1.0 release.
Symptom. apt update or the install downloads fail with an authorization error such as 401 or 403.
Likely cause. Binions packages come from an apt repository that is configured during install, and that repository is gated by an access token tied to your account. A 401 or 403 means the token is missing, wrong, or no longer valid.
Re-fetch, don’t hand-edit. The simplest fix is to copy a fresh install command from your customer portal at
https://portal.binions.io. It re-creates the repository entry with a current token, so you do not have to edit any files by hand.
After re-running the install command from the portal, refresh and retry:
sudo apt update
sudo apt install binions-<name>Symptom. The package installed, but binions-cliconsole status shows the daemon as DOWN (refused), or it never came up.
Likely cause. Installation and startup are separate concerns — a clean install does not guarantee a running daemon. Common reasons are a daemon’s own Redis not being up yet, a configuration error, or a port already in use.
Fix. Look at the daemon’s systemd state and logs to see the real error, then work through the startup checklist:
systemctl status binions-<name>
journalctl -u binions-<name> -n 100 --no-pagerFor the full sequence of checks — the daemon’s Redis, PostgreSQL, configuration, and ports — head to Daemon won’t start.
Once everything is in place, verify the install the same way the post-install checklist does — every daemon should report UP:
binions-cliconsole status # expect every daemon UPIf a row shows DEGRADED or DOWN instead of UP, that one daemon — not the install — needs attention; start with its logs above. Walk the full sequence in the post-install checklist.
* Raspberry Pi and other 64-bit ARM hardware are supported from the public 1.0 release. The current alpha packages are 64-bit x86 (amd64) only.