#Gateway unresponsive

1 messages · Page 1 of 1 (latest)

floral apex
#

I've set up Openclaw and it's stopped working. I've ran : rm ~/.openclaw/gateway.pid and it keeps prompting no such file or directory

oblique totemBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

graceful kestrelBOT
#

rm: ... No such file or directory just means ~/.openclaw/gateway.pid doesn’t exist on your machine (so there’s no stale PID file to delete). OpenClaw doesn’t rely on that file in many setups anymore, so deleting it usually won’t fix “gateway unresponsive”.

The fastest way to debug is to use the built-in status/log commands. On the machine running the Gateway, please run and paste the output of:

openclaw --version
openclaw gateway status
openclaw status --all
openclaw logs --follow

If you just want to try the “safe restart” first:

openclaw gateway restart
floral apex
#

When I run openclaw --version it prompts error: unknown option -version

graceful kestrelBOT
#

That error message (unknown option -version) is what you get when the CLI receives a single-dash flag (-version), not the double-dash one.

Can you try these and paste the output?

openclaw --version
openclaw -V
openclaw status

If all of those fail / look weird, it usually means you’re not running the OpenClaw binary you think you are. Then please also paste:

which openclaw
openclaw --help | head -40