Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix openclaw update does not update systemd service path after version upgrade [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#73457•Fetched 2026-04-29 06:19:42
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
YuchenNingYuchenNing
Participants
clawsweeper[bot]clawsweeper[bot]YuchenNingYuchenNing
Timeline (top)
closed ×1commented ×1

Root Cause

  • npm package updates to new version
  • systemd service still references old version path in ExecStart
  • Gateway fails with ERR_MODULE_NOT_FOUND because the old version's node_modules is incomplete

Fix Action

Workaround

Manually edit ~/.config/systemd/user/openclaw-gateway.service to update the version number in ExecStart path, then run:

systemctl --user daemon-reload
systemctl --user restart openclaw-gateway.service

Code Example

systemctl --user daemon-reload
systemctl --user restart openclaw-gateway.service
RAW_BUFFERClick to expand / collapse

Bug Description

After running openclaw update, the npm package is updated to the new version, but the systemd service file (~/.config/systemd/user/openclaw-gateway.service) still contains the hardcoded old version path, causing the gateway to fail to start.

Steps to Reproduce

  1. Install openclaw (e.g., version 2026.4.15)
  2. Gateway runs correctly via systemd
  3. Run openclaw update (package updates to 2026.4.26)
  4. Run systemctl --user restart openclaw-gateway.service
  5. Gateway fails to start - it tries to use the old version binary path

Expected Behavior

openclaw update should either:

  1. Update the systemd service file to point to the new version, OR
  2. Automatically reload/restart the systemd service

Actual Behavior

  • npm package updates to new version
  • systemd service still references old version path in ExecStart
  • Gateway fails with ERR_MODULE_NOT_FOUND because the old version's node_modules is incomplete

Environment

  • Platform: Tencent Cloud VM (OpenCloudOS)
  • Node: v22.22.0 via nvm
  • OpenClaw: 2026.4.26

Workaround

Manually edit ~/.config/systemd/user/openclaw-gateway.service to update the version number in ExecStart path, then run:

systemctl --user daemon-reload
systemctl --user restart openclaw-gateway.service

extent analysis

TL;DR

Update the ExecStart path in the systemd service file to point to the new version after running openclaw update.

Guidance

  • Verify the version number in the openclaw-gateway.service file matches the updated package version.
  • Manually update the ExecStart path in the service file to reference the new version, as described in the provided workaround.
  • Consider automating the update process for the systemd service file to prevent future manual interventions.
  • After updating the service file, run systemctl --user daemon-reload and systemctl --user restart openclaw-gateway.service to apply the changes.

Example

# Example update command for the service file
sed -i 's/2026.4.15/2026.4.26/g' ~/.config/systemd/user/openclaw-gateway.service

Notes

The provided workaround is a temporary solution. A more permanent fix would involve modifying the openclaw update command to automatically update the systemd service file or reload the service after updating.

Recommendation

Apply the workaround by manually updating the openclaw-gateway.service file and reloading the systemd service, as this is the most straightforward solution given the current information.

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…
#tool integration#LLM response#prompt template#agent execution#callback error

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 openclaw update does not update systemd service path after version upgrade [1 comments, 2 participants]