Boot-DM publish fails on startup — wait for a connected relay instead of a fixed sleep #48

New issue

Closed

opened 2026-06-27 10:02:41 +00:00 by padreug · 0 comments

padreug commented

2026-06-27 10:02:41 +00:00

Owner

On the aio-demo deploy of the nostr-tools build (#45), the boot-time admin DM failed at startup:

Error: publish failed on all relays after 5 attempts: relay not connected:
  wss://blastr.f7z.xyz; wss://nostr.mutinywallet.com
  at RelayPool.publish … at dmUser … at AdminInterface.notifyAdminsOfNewConnection

notifyAdminsOfNewConnection spins up a throwaway RelayPool to two external public relays, waits a fixed 2500ms, then publishes the DM. Those relays are often slow to connect, so the fixed wait (+ the ~1.2s publish retry budget) can elapse before any connection is up → the publish fails.

Non-critical: it's caught and logged by dmUser; the daemon reaches "ready to serve" before this and runs fine. But it's a noisy error on every boot when notifyAdminsOnBoot is set.

Fix: poll pool.connectedCount() > 0 up to a cap (~8s) before publishing, instead of the fixed sleep — succeed as soon as a relay is up, still best-effort (fall through + log if none connect). Small isolated change in admin/index.ts.

Refs: #45 (where the DM was ported to nostr-tools), #44.

On the `aio-demo` deploy of the nostr-tools build (#45), the boot-time admin DM failed at startup: ``` Error: publish failed on all relays after 5 attempts: relay not connected: wss://blastr.f7z.xyz; wss://nostr.mutinywallet.com at RelayPool.publish … at dmUser … at AdminInterface.notifyAdminsOfNewConnection ``` `notifyAdminsOfNewConnection` spins up a throwaway `RelayPool` to two **external** public relays, waits a fixed `2500ms`, then publishes the DM. Those relays are often slow to connect, so the fixed wait (+ the ~1.2s publish retry budget) can elapse before any connection is up → the publish fails. **Non-critical:** it's caught and logged by `dmUser`; the daemon reaches "ready to serve" before this and runs fine. But it's a noisy error on every boot when `notifyAdminsOnBoot` is set. **Fix:** poll `pool.connectedCount() > 0` up to a cap (~8s) before publishing, instead of the fixed sleep — succeed as soon as a relay is up, still best-effort (fall through + log if none connect). Small isolated change in `admin/index.ts`. Refs: #45 (where the DM was ported to nostr-tools), #44.

padreug referenced this issue from a commit

2026-06-27 10:03:31 +00:00

fix(admin): wait for a connected relay before the boot DM, not a fixed sleep (#48)

padreug referenced this issue from a pull request that will close it,

2026-06-27 10:03:50 +00:00

fix(admin): harden the boot DM — await a connected relay + guard teardown/rejection (#48, review CS-3) #49

padreug referenced this issue from a commit

2026-06-27 10:22:30 +00:00

fix(admin): harden the boot DM — guard teardown + unhandled rejection (review CS-3)

padreug referenced this issue from a commit

2026-06-27 11:19:51 +00:00

Merge pull request 'fix(admin): harden the boot DM — await a connected relay + guard teardown/rejection (#48, review CS-3)' (#49) from fix/boot-dm-await-connect into dev