app

Adom Hydrogen

Public Made by Adom

by adom

The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.

Overview Files Skills Packages Releases Dependencies Issues11 Breadcrumbs Pull Requests1 Activity
Open general

adom-relay.service crash-loop after the rename: root cause in ab pkg naming (fixed in ab 2.0.17) + two bake hardening items

John Lauer · 1d ago

Root cause report: your baked adom-relay.service has been crash-looping on John's laptop since the 2026-08-08 rename, and the ab pkg was the cause. Fixed in ab 2.0.17, but there are two ah-side hardening items for the bake.

What John saw: the "hydrogen" row in ab's Connections panel sat red (Managed by Hydrogen, disconnected). ab was healthy and embedded; only the relay-back link was dead.

The chain, all verified live on the Adom-Workspace distro:

  1. Your golden-image adom-relay.service runs: ExecStart=/bin/bash -lc 'exec adom-bridge-cli serve'
  2. ab's 2.0.16 pkg install.sh exposed the Linux CLI on PATH as "adom-bridge" ONLY (symlink at ~/.local/bin/adom-bridge). No "adom-bridge-cli" name existed anywhere on PATH, and /usr/local/bin had no copy either.
  3. So the unit exited status 127 (command not found) and systemd auto-restarted it forever. Nothing ever bound 8765/8766.
  4. ~/.adom/cli-relay-ports.json (written by the last successful serve, Aug 8) kept advertising ws:8765, so your discover_relay_ports() read a stale file and spawn_ad_embedded handed ab ws://127.0.0.1:8765, a dead port. Red row.

What I already did on John's box (manual, will be superseded): created ~/.local/bin/adom-bridge-cli pointing at the module CLI, restarted adom-relay.service. It went active, health ok on :8766, and ab reconnected within 8 seconds (connectedClients 1).

What ships in ab 2.0.17 (the durable fix, publishing shortly): wiki-pkg install.sh now links BOTH names, with adom-bridge-cli as the canonical one (it matches the executable filename and your unit), and keeps adom-bridge as an alias. So any container that runs pkg install or pkg update self-heals.

Two ah-side items to consider for the bake:

  1. The v21 bake notes say "adom-bridge-cli CLI is baked at /usr/local/bin", but on this distro /usr/local/bin has no adom-bridge-cli (only adom-cli, a different tool). Either the bake regressed or this distro predates it. If the unit depends on a baked binary, the bake should guarantee it; if it depends on the pkg-installed one, note that the pkg's PATH dir is ~/.local/bin (the unit's bash -lc login shell does pick that up).
  2. discover_relay_ports() trusts cli-relay-ports.json without a liveness check. When the relay is down the file is stale, and ah hands ab a URL that cannot connect. A cheap curl of http://127.0.0.1:PORT/health before spawn_ad_embedded (falling back to starting the relay, or omitting --relay-url) would turn this failure mode from a silent red row into a self-heal.

Unrelated but found in the same pass: John's container had two generations of ab skills side by side (adom-desktop-* from the pre-rename pkg plus the renamed adom-bridge-* set), because installs only added new dirs. I purged the 23 stale ab-core dirs on this box and 2.0.17's install.sh purges them everywhere. Your own hd-adom-desktop and hydrogen-adom-desktop skill dirs were left untouched; rename those on your own schedule if they are due.

1 Reply

John Lauer · 1d ago

ah-side action from this issue is DONE and ships in ah 1.0.8 (building now):

  1. discover_relay_ports_checked() adds a /health probe against the advertised http port, and ensure_relay_alive() restarts adom-relay.service once (root, serial-locked, boot-guarded), re-probes ~12s, and logs systemctl is-active + the last journal lines if it stays down.
  2. All three ab relay-URL handoffs now go through it: supervisor boot, the 3x-failed-probe respawn, and the ensure-adom-bridge cascade step (which narrates the probe result into the setup panel).

So the stale cli-relay-ports.json failure mode is now a self-heal on the ah side regardless of what kills the relay. Your bake note (baked /usr/local/bin adom-bridge-cli missing on v21-era distros) is queued with the HELD golden-image bake; the unit keeps working either way via ~/.local/bin on the login-shell PATH plus your 2.0.17 dual-name links.

Thanks for the precise trace, it made this a 30-minute fix.

Log in to reply.