Repository navigation
Description
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
- Upgrade OpenClaw from 2026.5.7 to 2026.5.18 or 2026.5.19 via npm install -g
- Run
openclaw status - Observe the command hangs for >10s
- Observe exit code 124 (timeout)
- 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.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon May 20, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 30, 2026, 7:16 PM ET / 23:16 UTC.
Summary
Keep open: current main and the latest release still leave the Linux
openclaw statusservice-summary path able to block on unboundedsystemctlreads, while the linked closing PR is still open and unmerged.Reproducibility: yes. Source inspection shows the status timeout is not propagated into Linux service-summary/systemctl reads, and the linked PR includes before/after component proof against a wedged
systemctlsubprocess.Root-cause cluster
Relationship:
canonicalCanonical: #84698
Summary: This issue is the canonical Linux
openclaw status/systemctl hang tracker; the open PR is the candidate fix, while macOS, Windows, and Docker-probe items overlap only by status-hang theme or adjacent subprocess paths.Members:
fixed_by_candidate: fix(status): bound systemd service probes so status cannot hang on a wedged systemctl (#84698) #94149 - The open PR uses closing syntax for this issue and threads timeouts through the implicated Linux status service-summary/systemd read path.partial_overlap: openclaw status CLI command hangs before connecting to gateway (v2026.5.18) #84012 - The open macOS report shares the broaderopenclaw statushang symptom but reports Darwin behavior before gateway connection, not Linux systemctl.partial_overlap: Windows: openclaw status / status --json hangs in 2026.5.18 while status --all succeeds #84001 - The open Windows report shares the service-summary timeout theme but implicates Scheduled Task/schtasks behavior outside the Linux systemd path.adjacent_distinct: fix(status): bound deep docker audit probes #85476 - The merged PR bounded Docker audit probes forstatus --deep, a different subprocess path from Linux service-summarysystemctlreads.Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.
Next step
Do not queue a new repair job because #94149 is already the open closing PR for the implicated Linux systemd timeout path.
Review details
Best possible solution:
Review and land #94149, or an equivalent timeout-threading fix for Linux service-manager reads, then close this issue as implemented.
Do we have a high-confidence way to reproduce the issue?
Yes. Source inspection shows the status timeout is not propagated into Linux service-summary/systemctl reads, and the linked PR includes before/after component proof against a wedged
systemctlsubprocess.Is this the best way to solve the issue?
Yes, the open linked PR is the narrow maintainable fix shape: forward the existing status deadline into read-only service-manager probes and degrade the service row instead of hanging. This issue should remain open until that PR or an equivalent fix merges.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning high; reviewed against 3811001d2783.
Label changes
Label changes:
maturity:stable: The issue affects CLI Observability and Linux Gateway host diagnostics/status behavior, both under M4 Stable surfaces inqa/maturity-scores.yaml.Label justifications:
P2: The report is a concrete diagnostic CLI availability regression with cron/audit impact, but it does not make the whole runtime unusable.impact:crash-loop: The failure mode is a process-level hang until an external timeout killsopenclaw status.maturity:stable: The issue affects CLI Observability and Linux Gateway host diagnostics/status behavior, both under M4 Stable surfaces inqa/maturity-scores.yaml.Evidence reviewed
What I checked:
AGENTS.md:12, 3811001d2783)resolveStatusRuntimeDetailsreceivestimeoutMsand uses it for gateway calls, but callsresolveStatusServiceSummaries()without a deadline. (src/commands/status-runtime-shared.ts:293, 3811001d2783)readServiceStatusSummarycallsreadGatewayServiceState(service, { env: process.env }), andreadGatewayServiceStaterunsisLoadedandreadRuntimewith no timeout argument. (src/commands/status.service-summary.ts:38, 3811001d2783)execSystemctlcallsexecFileUtf8("systemctl", args, { env: ... })with notimeout;isSystemdServiceEnabledandreadSystemdServiceRuntimereach that wrapper. (src/daemon/systemd.ts:545, 3811001d2783)v2026.6.11points ate085fa1a3ffd32d0ea6917e1e6fb4ecbffbb77d2; its status runtime still calls service summaries without forwardingtimeoutMs, and its systemd wrapper has no timeout. (src/commands/status-runtime-shared.ts:219, e085fa1a3ffd)systemctlproof. (e0f4df946e7d)Likely related people:
src/daemon/systemd.ts)src/commands/status-runtime-shared.ts,src/daemon/service.ts,src/daemon/systemd.ts)readSystemdServiceRuntimeandisSystemdServiceEnabledarea implicated by the hang. (role: adjacent systemd contributor; confidence: medium; commits: b988e2f92b0c; files:src/daemon/systemd.ts)systemctlproof. (role: candidate fix author; confidence: high; commits: e0f4df946e7d; files:src/commands/status-runtime-shared.ts,src/commands/status.service-summary.ts,src/daemon/service.ts)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.merge: resolve upstream/main conflict in systemd.test.ts (openclaw#94149
fix(status): bound systemd service probes so status cannot hang on a …
fix(status): bound systemd service probes so status cannot hang on a …
fix(status): bound systemd service probes so status cannot hang on a …