#openclaw gateway restart

1 messages · Page 1 of 1 (latest)

raven pike
#

I tried to conduct openclaw gateway restart, however I got
🦞 OpenClaw 2026.2.14 (unknown) — I don't just autocomplete—I auto-commit (emotionally), then ask you to review (logically).

Invalid config at /home/node/.openclaw/openclaw.json:\n- channels.discord: Unrecognized key: "requireMention"
│
◇ Config ───────────────────────────────────────────────────╮
│ │
│ Config invalid; doctor will run with best-effort config. │
│ │
├────────────────────────────────────────────────────────────╯
│
◇ Unknown config keys ───────────────╮
│ │
│ - channels.discord.requireMention │
│ │
├─────────────────────────────────────╯
│
◇ Doctor ────────────────────────────────────────────╮
│ │
│ Run "openclaw doctor --fix" to remove these keys. │
│ │
├─────────────────────────────────────────────────────╯
Config invalid
File: ~/.openclaw/openclaw.json
Problem:

  • channels.discord: Unrecognized key: "requireMention"

Run: openclaw doctor --fix
Config invalid
File: ~/.openclaw/openclaw.json
Problem:

  • channels.discord: Unrecognized key: "requireMention"

Run: openclaw doctor --fix
Gateway service check failed: Error: systemctl --user unavailable: unknown error
what doed that means and what should I do?

drifting lanternBOT
#

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

thick elbowBOT
#

That’s two separate issues:

1) Config error: channels.discord.requireMention no longer exists

In 2026.2.14, requireMention is not a top-level Discord key. It’s configured per guild and optionally per channel.

So you should remove the old key, or move it to the new location.

Fast fix (auto-removes unknown keys):

openclaw doctor --fix

Or surgically remove just that one key:

openclaw config unset channels.discord.requireMention
#

If what you wanted was “bot only responds when mentioned” in a guild/channel, do it like this:

{
  channels: {
    discord: {
      guilds: {
        "123456789012345678": {
          requireMention: true,
          channels: {
            "1472557462682075343": { requireMention: true }
          }
        }
      }
    }
  }
}
#

Docs: https://docs.openclaw.ai/channels/discord (see “Mentions and group DMs”)

2) systemctl --user unavailable

openclaw gateway restart is trying to manage a systemd user service, but your environment doesn’t have systemctl --user available (common in Docker containers, or WSL2 without systemd enabled, or minimal distros).

What to do depends on where you’re running:

  • If you’re in Docker: restart the container, or just run the gateway in the foreground:
    openclaw gateway --force
  • If you’re on WSL2: you likely need to enable systemd first. Follow: https://docs.openclaw.ai/platforms/windows#wsl2 (section “Enable systemd”).