#/restart in Telegram doesn't bring gateway back online

6 messages · Page 1 of 1 (latest)

amber geyser
#

Hi, I restarted my OpenClaw through /restart command.

The message sends me back it will be back in a few seconds

This has been 10min ago and no response on a /status check

Any recommendation how to get this function to work trustworthy?

hardy horizonBOT
nimble baneBOT
#

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

hardy horizonBOT
valid grottoBOT
#

10 minutes is not normal, /restart should be seconds, not minutes.

First, please paste this from the gateway host:

openclaw --version
openclaw gateway status
openclaw status --all

If Telegram still stays quiet after that, also run:

openclaw channels status
openclaw channels logs --channel telegram
#

What I’d look for:

  • Runtime: running + RPC probe: failed
    = service came back, but the gateway itself did not boot cleanly.
  • RPC probe: ok, but Telegram is bad
    = gateway is up, channel reconnect is the actual problem.

For making /restart trustworthy, the big one is this:

  • use the installed background service (systemd / launchd / schtasks)
  • do not rely on a foreground openclaw gateway terminal session
  • keep the host awake and online, if the machine sleeps, chat /restart cannot save it
  • leave channel health monitoring enabled, default is every 5 minutes

Docs: