AgentFixboard
UnverifiedLast checked OpenClaw#regression#setup#error-messages

openclaw update from 2026.9.4 stops with reason code doctor-failed and rolls back

openclaw update from 2026.9.4 toward 2026.9.5 spends minutes on Phase: repairing and then exits. The reason code is doctor-failed. There is no Upgraded successfully, Reverted, or Aborted line.

From GitHub

openclaw/openclaw

Issue

Difficulty
Moderate
Time
~15 min
Steps
3
Fixed in
—
Last checked

Unverified: we could not confirm from the sources that a fix shipped. Source: issue closed as completed; the release that contains the pull requests is not named. Last checked 2026-10-18.

Symptom

openclaw update from 2026.9.4 toward 2026.9.5 spends minutes on Phase: repairing and then exits. The reason code is doctor-failed. There is no Upgraded successfully, Reverted, or Aborted line.

Evidence what you'll see

  • The report file records Result: error, Reason code: doctor-failed, Before version: 2026.9.4, and Rollback outcome: verified safe to restart.
  • After the run, npm list -g openclaw still reported openclaw@2026.9.4.
  • A maintainer comment names the line Doctor could not enter maintenance on the finalize path, and says an earlier Doctor complete. line in the tail was the repair rehearsal, not the lint finishing.

Why it happens

The report's candidate checks run in validating and again in repairing, and on the hosts in the thread that sum crosses the updater's 300 second budget. A second failure on the same issue is a deadlock: the updater holds Gateway activation, then asks Doctor to enter maintenance, and Doctor refuses because that activation is held.

Affected versions

The report is macOS darwin/x64, Node 26.8.2, npm update mode, OpenClaw 2026.9.4 (3a9d69d) toward npm dist-tag latest 2026.9.5. A later comment names Linux x64, kernel 7.2.5-200.fc44, Node v24.19.0, channel stable.

Fix steps

0 of 3 done

Your check marks stay in this browser only.

How to check it worked

  • openclaw --version prints OpenClaw 2026.9.4 (3a9d69d) after a failed attempt, or a later attempt gets past Phase: repairing without reason code doctor-failed.

If it still fails

  • The sanitized report is written under ~/.openclaw/update-reports/ after the process exits. The linked issue does not name an npm flag that forces the 2026.9.5 install through.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it