Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix doctor: warn and continue when cron store is unreadable [1 pull requests]

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…

openclaw doctor can abort while checking cron if the cron job store exists but is unreadable by the OpenClaw runtime user. In this state, doctor reports the underlying permission problem but does not finish the rest of the health checks.

Error Message

Doctor should warn that the cron store is unreadable and continue with the remaining checks, similar to how other non-fatal environment/config issues are reported. I pushed a small branch on my fork that changes the cron doctor path to warn and continue when the cron store cannot be read:

Root Cause

openclaw doctor can abort while checking cron if the cron job store exists but is unreadable by the OpenClaw runtime user. In this state, doctor reports the underlying permission problem but does not finish the rest of the health checks.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Summary

openclaw doctor can abort while checking cron if the cron job store exists but is unreadable by the OpenClaw runtime user. In this state, doctor reports the underlying permission problem but does not finish the rest of the health checks.

Repro / observed state

On a Docker install, these files were owned by root:root with mode 0600:

  • /home/node/.openclaw/openclaw.json
  • /home/node/.openclaw/cron/jobs.json

Running openclaw doctor hit the unreadable cron store during the cron checks. The practical effect is that doctor cannot complete cleanly, so it is harder to see what else is left to fix.

Expected behavior

Doctor should warn that the cron store is unreadable and continue with the remaining checks, similar to how other non-fatal environment/config issues are reported.

Candidate fix

I pushed a small branch on my fork that changes the cron doctor path to warn and continue when the cron store cannot be read:

https://github.com/ericpearson/openclaw/tree/fix/doctor-unreadable-cron-store

Commit: e57c341f53

Focused test result from the upstream-based worktree: src/commands/doctor-cron.test.ts passed with 16 tests.

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

Doctor should warn that the cron store is unreadable and continue with the remaining checks, similar to how other non-fatal environment/config issues are reported.

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 doctor: warn and continue when cron store is unreadable [1 pull requests]