openclaw - 💡(How to fix) Fix [Bug]: openclaw status hangs and times out — regression from 2026.5.7

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…

The openclaw status command hangs and exits with code 124 after upgrading from 2026.5.7 to 2026.5.18+. The health command works fine.

Root Cause

The openclaw status command hangs and exits with code 124 after upgrading from 2026.5.7 to 2026.5.18+. The health command works fine.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The openclaw status command hangs and exits with code 124 after upgrading from 2026.5.7 to 2026.5.18+. The health command works fine.

Steps to reproduce

  1. Upgrade OpenClaw from 2026.5.7 to 2026.5.18 or 2026.5.19 via npm install -g
  2. Run openclaw status
  3. Observe the command hangs for >10s
  4. Observe exit code 124 (timeout)
  5. Also try openclaw status --timeout 5000 — still hangs

Expected behavior

In 2026.5.7, openclaw status returned channel health status and recent session recipients within 2-3 seconds.

Actual behavior

Command spawns multiple subprocesses, triggers SIGALRM after ~10 seconds, then receives SIGTERM and exits with code 124. No output produced. strace shows setsockopt calls before the hang. openclaw health --json works fine and returns instantly.

OpenClaw version

2026.5.19 (a185ca2), also reproduced on 2026.5.18

Operating system

Ubuntu 24.04, Linux 6.8.0-71-generic x86_64

Install method

npm global

Model

deepseek/deepseek-v4-pro

Provider / routing chain

deepseek (direct API)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected: All users running openclaw status after upgrading to 2026.5.18+ Severity: Medium (blocks diagnostic command and healthcheck cron) Frequency: Always (5/5 observed attempts) Consequence: Weekly security audit cron fails with timeout (healthcheck:security-audit depends on openclaw status --deep)

Additional information

Last known good: 2026.5.7. First known bad: 2026.5.18. Node.js v22.22.2. Same behavior on both 2026.5.18 and 2026.5.19.

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…

FAQ

Expected behavior

In 2026.5.7, openclaw status returned channel health status and recent session recipients within 2-3 seconds.

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 [Bug]: openclaw status hangs and times out — regression from 2026.5.7