#two gateways

1 messages · Page 1 of 1 (latest)

calm atlas
#

Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Command: /usr/bin/node /usr/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (pid 52221, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: admin-capable

Listening: 127.0.0.1:18789
Other gateway-like services detected (best effort):

  • openclaw-master.service (system, unit: /etc/systemd/system/openclaw-master.service)
    Cleanup hint: systemctl --user disable --now openclaw-gateway.service
    Cleanup hint: rm ~/.config/systemd/user/openclaw-gateway.service

Recommendation: run a single gateway per machine for most setups. One gateway supports multiple agents (see docs: /gateway#multiple-gateways-same-host).
If you need multiple gateways (e.g., a rescue bot on the same host), isolate ports + config/state (see docs: /gateway#multiple-gateways-same-host).

Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

sweet sealBOT
#

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

toxic citrusBOT
#

This gateway itself looks healthy: running, listening on 127.0.0.1:18789, probe OK.

The only real flag is the extra system service:

openclaw-master.service

First, please paste:

openclaw --version

Then pick one gateway to keep:

If openclaw-master.service was not intentional

#

Keep the working user service and disable the system one:

sudo systemctl disable --now openclaw-master.service
openclaw gateway status --deep

Don’t delete the unit file until you confirm everything still works.

If openclaw-master.service is the intended gateway

Disable the user-level duplicate instead:

systemctl --user disable --now openclaw-gateway.service
openclaw gateway status --deep
calm atlas
#

OpenClaw 2026.4.25 (aa36ee6)

toxic citrusBOT
#

Thanks — 2026.4.25 is fine. This now looks like a which gateway should own the machine? cleanup issue.

First inspect the extra system service:

sudo systemctl status openclaw-master.service --no-pager -l
sudo systemctl cat openclaw-master.service

If openclaw-master.service is not intentional, disable that one:

sudo systemctl disable --now openclaw-master.service
openclaw gateway status --deep

If openclaw-master.service is your intended gateway, follow the cleanup hint and disable the duplicate user service:

# 
systemctl --user disable --now openclaw-gateway.service
openclaw gateway status --deep

Don’t delete unit files yet; stop/disable first, confirm one gateway remains healthy, then clean files later if needed.

Docs: https://docs.openclaw.ai/gateway/multiple-gateways

calm atlas
#

Loaded: loaded (/etc/systemd/system/openclaw-master.service; disabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2026-04-27 08:20:15 BST; 6h ago
Duration: 11ms
Main PID: 1501 (code=exited, status=200/CHDIR)
CPU: 1ms

Apr 27 08:20:15 ubuntu systemd[1]: openclaw-master.service: Main process exited, code=exited, status=200/CHDIR
Apr 27 08:20:15 ubuntu systemd[1]: openclaw-master.service: Failed with result 'exit-code'.
Apr 27 08:20:15 ubuntu systemd[1]: openclaw-master.service: Scheduled restart job, restart counter is at 5.
Apr 27 08:20:15 ubuntu systemd[1]: openclaw-master.service: Start request repeated too quickly.
Apr 27 08:20:15 ubuntu systemd[1]: openclaw-master.service: Failed with result 'exit-code'.
Apr 27 08:20:15 ubuntu systemd[1]: Failed to start openclaw-master.service - OpenClaw Master Gateway (Telegram + main Discord).

toxic citrusBOT
#

Yep — that confirms openclaw-master.service is just a stale/broken system unit, not a second healthy gateway.

status=200/CHDIR means systemd couldn’t cd into the service’s WorkingDirectory before starting it. Since it’s also disabled and your user gateway is healthy, I’d clean up the stale system unit:

sudo systemctl reset-failed openclaw-master.service
sudo mv /etc/systemd/system/openclaw-master.service "$HOME/openclaw-master.service.bak"
sudo systemctl daemon-reload

openclaw gateway status --deep

After that, the “Other gateway-like services detected” warning should disappear.

If you actually intended openclaw-master.service to be the real gateway, don’t move it yet — paste: