Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix openclaw status CLI command hangs before connecting to gateway (v2026.5.18) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#84012•Fetched 2026-05-20 03:45:20
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
Andy283Andy283
Participants
Andy283Andy283clawsweeper[bot]clawsweeper[bot]
Timeline (top)
labeled ×4commented ×1

openclaw status hangs indefinitely when run from the CLI in v2026.5.18. It produces no stdout/stderr and gets killed by SIGKILL (exit 124 with timeout).

Error Message

The missing module error Cannot find module task-registry.maintenance-B-jsfe-3.js imported from status.summary-CZND_jzu.js from the initial update doctor (v2026.5.12 runtime) is no longer present after restart; the v2026.5.18 build has different chunk hashes.

Root Cause

openclaw status hangs indefinitely when run from the CLI in v2026.5.18. It produces no stdout/stderr and gets killed by SIGKILL (exit 124 with timeout).

RAW_BUFFERClick to expand / collapse

Description

openclaw status hangs indefinitely when run from the CLI in v2026.5.18. It produces no stdout/stderr and gets killed by SIGKILL (exit 124 with timeout).

Steps to Reproduce

  1. Ensure Gateway is running (confirmed openclaw gateway status returns healthy).
  2. Run openclaw status.
  3. Command blocks indefinitely with zero output.

Expected Behavior

openclaw status should connect to the Gateway, fetch status, and print channel health + session summary, then exit promptly (default timeout 10s).

Actual Behavior

  • Exit code: 124 (timeout after 15s)
  • Output: empty
  • Gateway logs: zero new entries while the command is running (confirmed by comparing log file size before/after) — meaning the CLI hangs during initialization, before even attempting a WebSocket connection to the Gateway.

Diagnostics

DiagnosticResult
openclaw gateway status✅ Works normally
openclaw session list --limit 1✅ Works normally
openclaw doctor✅ Works normally
openclaw channels status --probe✅ Works normally
openclaw status --json❌ Hangs (same as plain)
openclaw status --timeout 5000❌ Hangs (same)
openclaw status --all❌ Hangs (same)

The missing module error Cannot find module task-registry.maintenance-B-jsfe-3.js imported from status.summary-CZND_jzu.js from the initial update doctor (v2026.5.12 runtime) is no longer present after restart; the v2026.5.18 build has different chunk hashes.

Environment

  • OpenClaw: 2026.5.18 (50a2481)
  • Node.js: v24.15.0
  • OS: macOS 15.7.5 (Darwin x64)
  • Install method: npm global install (openclaw@latest)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#response parsing#generation error#database connection#vector store#embedding generation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix openclaw status CLI command hangs before connecting to gateway (v2026.5.18) [1 comments, 2 participants]