After every upgrade, run this short list of checks to confirm the platform came back up cleanly. A Binions upgrade restarts the affected daemons automatically, so the job here is simply to verify the result: every service is up, all packages report the same new version, nothing is stuck restarting, and recent logs are clean. The whole pass takes a couple of minutes and is worth doing every time.
Good to know. The first command,
binions-cliconsole status, already answers most of the checklist — it rolls up every daemon’s readiness into one table. The remaining steps confirm versions, restart counts, and logs.
Work through these in order. Each step builds on the last, so a green result at the top usually means the rest will follow.
UP with a 200.binions-* package should report the same new version — the platform always ships as one release at one version, so a mismatch means an upgrade didn’t complete.0 after the upgrade.Steps 1, 2 and 5 are single commands:
# 1. All daemons up — every service should read UP (200)
binions-cliconsole status
# 2. Versions match — all binions-* packages report the same new version
apt list --installed 'binions-*'
# 5. Playbooks still valid
binions-cliconsole validateSteps 3 and 6 are run per daemon — substitute the short name of each service (for example logger, mailbox, scheduler):
# 3. No restart loops — should print 0 for each daemon
systemctl show -p NRestarts --value binions-logger
# 6. Recent logs clean — look for a normal boot, no licence/Redis errors
journalctl -u binions-logger -n 50 --no-pagerTip. If the
statustable is all green and every package shows the same version, you’re done — the per-daemon restart and log checks are there to confirm any service that the rollup flagged, or just for extra peace of mind.
A failed check almost always points to a specific, recoverable problem:
binions-* package lands on the same release; if you crossed a licence boundary, the major-version gate may have intentionally held a package back.Before you roll back, back up. Rolling back changes the installed software, not your data. Always capture a fresh backup before downgrading so you can recover if the older release expects different state.