openclaw - 💡(How to fix) Fix [Bug]: Linux 通过 npm 全局安装 openclaw 时，openclaw doctor 误报 gateway 错误：nohup: 无法运行命令 'openclaw-gateway': 没有那个文件或目录 [1 participants]

问题摘要\n\n在 Linux 上通过 npm install -g openclaw 全局安装 openclaw 后，运行 openclaw doctor 会误报 gateway 错误。原因是 doctor 的探测逻辑尝试执行 nohup openclaw-gateway，但 npm 包在 Linux 上并未附带 openclaw-gateway 这个独立二进制文件。而实际上 systemd 用户服务已经正确回退到 node dist/index.js gateway 启动，gateway 运转完全正常，只是 doctor 给出了错误的负面报告。\n\n## 环境信息\n\n- OpenClaw 2026.3.28\n- Linux（用户级 systemd）\n- 安装方式：npm install -g openclaw\n\n## 实际表现\n\n运行 openclaw doctor 时显示：\n\n\nLast gateway error: nohup: 无法运行命令 'openclaw-gateway': 没有那个文件或目录\n\n\n而由 openclaw doctor --fix 生成的 systemd 用户服务（~/.config/systemd/user/openclaw-gateway.service）中，ExecStart 实际为：\n\nini\nExecStart=/usr/bin/node /home/<user>/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789\n\n\n这个启动方式是正常的 — systemctl --user status openclaw-gateway 显示 active (running)，Discord/Telegram 等 channel 也能正常登录和处理消息。问题仅在于 doctor 的某些探测分支仍试图直接调用 openclaw-gateway 二进制，而它在 Linux npm 安装场景中本来就不存在。\n\n## 预期表现\n\nopenclaw doctor 应当识别：在 Linux npm 安装环境下，gateway 的合法入口是 node <package>/dist/index.js gateway，而非独立的 openclaw-gateway 二进制，因此不应将此情况报告为错误。\n\n## 相关 issue\n\n- 可能与 #54740 属于同一类 doctor 误报问题。

TL;DR

Update the openclaw doctor logic to recognize the correct gateway entry point on Linux systems installed via npm.

Guidance

• Review the openclaw doctor code to identify where it attempts to execute nohup openclaw-gateway and update this logic to use the correct entry point for Linux systems installed via npm, which is node <package>/dist/index.js gateway.
• Verify that the systemd user service is correctly configured and running by checking the status with systemctl --user status openclaw-gateway.
• Consider updating the openclaw doctor documentation to reflect the correct expected behavior on Linux systems installed via npm.
• Investigate the related issue #54740 to determine if it is a similar doctor misreporting problem.

Example

No code example is provided as the issue does not contain sufficient information to generate a specific code snippet.

Notes

The solution may require updates to the openclaw doctor code and documentation. The issue may be specific to Linux systems installed via npm, and the solution may not apply to other installation methods or operating systems.

Recommendation

Apply a workaround by updating the openclaw doctor logic to recognize the correct gateway entry point on Linux systems installed via npm, as this is a more targeted solution than upgrading to a potentially non-existent fixed version.