Skip to content

[Bug]: openclaw status hangs and times out — regression from 2026.5.7 #84698

Closed

Description

@zus-assistant

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.

Activity

  1. clawsweeper commented on May 20, 2026

    @clawsweeper
    Contributor

    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 status service-summary path able to block on unbounded systemctl reads, 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 systemctl subprocess.

    Root-cause cluster
    Relationship: canonical
    Canonical: #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:

    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 systemctl subprocess.

    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:

    • No full end-to-end Linux CLI reproduction was run in this read-only review; the current source path and the linked PR's component proof are the evidence for keeping this open.

    Codex review notes: model internal, reasoning high; reviewed against 3811001d2783.

    Label changes

    Label changes:

    • add maturity:stable: The issue affects CLI Observability and Linux Gateway host diagnostics/status behavior, both under M4 Stable surfaces in qa/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 kills openclaw status.
    • maturity:stable: The issue affects CLI Observability and Linux Gateway host diagnostics/status behavior, both under M4 Stable surfaces in qa/maturity-scores.yaml.
    Evidence reviewed

    What I checked:

    Likely related people:

    • vincentkoc: Recent path history touches the central Linux systemd wrapper and service-status scope used by this issue. (role: recent status/systemd area contributor; confidence: high; commits: 64785823d093, 97d35f4c575b; files: src/daemon/systemd.ts)
    • steipete: History shows repeated work on the shared status runtime and daemon service-state flow that this issue now exercises. (role: feature-history contributor; confidence: high; commits: 258a214bcbff, f0b3c4164f61, 2761e8cc3b1a; files: src/commands/status-runtime-shared.ts, src/daemon/service.ts, src/daemon/systemd.ts)
    • yetval: Recent Linux system-scope detection work changed the same readSystemdServiceRuntime and isSystemdServiceEnabled area implicated by the hang. (role: adjacent systemd contributor; confidence: medium; commits: b988e2f92b0c; files: src/daemon/systemd.ts)
    • ZengWen-DT: The open linked PR changes the exact status service-summary/systemd timeout path and includes component-level wedged-systemctl proof. (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 keeps one durable marker-backed review comment per issue or PR.
    • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
    • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
    • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
    • Maintainers can also comment @clawsweeper review to request a fresh review only.
    • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
    • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
    • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.
  2. added
    P2Normal backlog priority with limited blast radius.
    impact:crash-loopCrash, hang, restart loop, or process-level availability failure.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    on May 20, 2026
  3. added
    clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.
    clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.
    and removed
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    on Jun 18, 2026
  4. added
    maturity:stableBroken existing behavior primarily owned by an M4/M5 scorecard surface.
    on Jun 30, 2026
  5. locked as resolved and limited conversation to collaborators on Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:crash-loopCrash, hang, restart loop, or process-level availability failure.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.maturity:stableBroken existing behavior primarily owned by an M4/M5 scorecard surface.regressionBehavior that previously worked and now fails

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions