openclaw-diagnoselisted

# OpenClaw Diagnose When the user asks you to diagnose or fix OpenClaw gateway/node issues, follow this structured investigation. ## Step 1: Gather status Run these in parallel: ```bash openclaw gateway status openclaw node status openclaw nodes status openclaw nodes pending ``` ## Step 2: Analyze warnings Look for these common issues: ### Multiple gateway-like services detected - Check if both `ai.openclaw.gateway` and `ai.openclaw.node` are registered as LaunchAgents - Use `launchctl print gui/$(id -u)/<label>` to inspect each service - Use `lsof -iTCP:<port> -sTCP:LISTEN -P` to confirm which process owns the port - The gateway **listens** on the port; the node host **connects to** the gateway on that port — they do NOT conflict ### Pairing required errors - Check `~/.openclaw/logs/node.err.log` for `pairing required` or `ECONNREFUSED` - If the node shows "pairing required", run `openclaw nodes pending` to find the pending request - Approve with: `openclaw nodes approve <requestId>` - **Pairing requests expire quickly** — if approval fails with "unknown requestId", restart the node (`openclaw node restart`) and immediately re-check pending + approve ### ECONNREFUSED errors - The gateway may not be running yet when the node starts - Check if gateway is listening: `lsof -iTCP:<port> -sTCP:LISTEN -P` - If gateway is down: `openclaw gateway restart` - The node has `KeepAlive: true` so it will automatically reconnect once the gateway is up ## Step 3: Verify fix After