Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Gateway entrypoint mismatch warning (entry.js → index.js) reappears after every openclaw update on Linux/systemd [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#59226•Fetched 2026-04-08 02:27:15
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
holgergruenhagenholgergruenhagen
Participants
holgergruenhagenholgergruenhagensiubing05siubing05
Timeline (top)
commented ×1

After every openclaw update, the doctor check shows:

Gateway service entrypoint does not match the current install — entry.js → index.js

This happens consistently, even on the latest version (v2026.4.1), and the service itself is actually correct the whole time.

Root Cause

Root cause (best guess)

Fix Action

Workaround

Run after every update:

openclaw gateway restart

Code Example

openclaw gateway restart
RAW_BUFFERClick to expand / collapse

Summary

After every openclaw update, the doctor check shows:

Gateway service entrypoint does not match the current install — entry.js → index.js

This happens consistently, even on the latest version (v2026.4.1), and the service itself is actually correct the whole time.

Environment

  • OS: Linux (Ubuntu), systemd user service
  • OpenClaw version: v2026.4.1 (da64a97)
  • Install method: npm global (/usr/lib/node_modules/openclaw)

What happens

  1. Run openclaw update
  2. After update, doctor warns: "Gateway service entrypoint does not match the current install (entry.js → index.js)"
  3. Running openclaw gateway restart (or openclaw doctor --fix) clears the warning immediately
  4. The actual systemd ExecStart was pointing to index.js the entire time — it was never wrong

Root cause (best guess)

When doctor runs during/after an update, process.argv[1] resolves to dist/entry.js (the CLI respawn wrapper). The doctor logic compares that against the service's ExecStart path, which correctly uses dist/index.js. This triggers a false mismatch warning.

After a gateway restart, the service file gets rewritten with the correct entrypoint and the warning disappears.

Workaround

Run after every update:

openclaw gateway restart

Related issues

This appears to be a recurring variant of existing reports:

  • #28423 — macOS: LaunchAgent entrypoint stale after update (entry.js → index.js)
  • #40811 — Gateway entrypoint mismatch after openclaw update — plist not reinstalled
  • #41144 — macOS: LaunchAgent still points to old dist/entry.js after upgrade
  • #45645 — Linux: doctor/update can leave CLI and gateway on different installs

The macOS-side issues have been around since February. Flagging here that the same symptom is still reproducible on Linux/systemd with the latest release.

Thanks for the great project! 🙏

extent analysis

TL;DR

Run openclaw gateway restart after every update to clear the false mismatch warning.

Guidance

  • The issue seems to be caused by the doctor logic comparing the wrong entrypoint during/after an update, triggering a false mismatch warning.
  • Verify that the actual systemd ExecStart is pointing to index.js to confirm that the service itself is correct.
  • To mitigate the issue, run openclaw gateway restart after every update, as this rewrites the service file with the correct entrypoint and clears the warning.
  • Consider monitoring related issues (#28423, #40811, #41144, #45645) for potential fixes or updates that may address the root cause.

Notes

The provided workaround may not be a permanent fix, but rather a temporary solution to clear the warning until the root cause is addressed.

Recommendation

Apply workaround: running openclaw gateway restart after every update is a simple and effective way to clear the false mismatch warning, even if it doesn't address the underlying issue.

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…
#retriever error#indexing error#inference speed#output truncation#response parsing

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]: Gateway entrypoint mismatch warning (entry.js → index.js) reappears after every openclaw update on Linux/systemd [1 comments, 2 participants]