#Discord & Telegram unresponsive

1 messages · Page 1 of 1 (latest)

lunar cairn
#

Both Discord & Telegram is responsive to write messages. Discord keeps disconnecting the bots before they response. Something is hanging after 4.25 update it seems like

slate oysterBOT
#

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

quick swallowBOT
#

That smells like a Gateway/session turn hanging, not Discord/Telegram token auth.

First, please check version — if you’re on 2026.4.25, update first; npm latest I see right now is 2026.4.26.

openclaw --version
openclaw update
openclaw doctor
openclaw gateway restart
openclaw channels status --probe

Then reproduce once and watch logs:

openclaw logs --follow
#

Look for these especially:

  • Discord: Listener DiscordMessageListener timed out, Slow listener detected, discord inbound worker timed out, websocket reconnect/handshake errors
  • Telegram: Polling stall detected, Network request for 'getUpdates' failed, TypeError: fetch failed
  • Gateway/session: stuck lane, provider timeout, active memory timeout, model/tool call hanging

If it still happens on latest, generate a sanitized diagnostics bundle and file it as a bug:

openclaw gateway diagnostics export

Docs: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/gateway/troubleshooting
Issues: https://github.com/openclaw/openclaw/issues

lunar cairn
#

It also happens on the latest version - I just noticed the problem starting on 04.25 version.
errors i see in the log:
02:58:55+00:00 info Completion cache update failed: Error: spawnSync /usr/bin/node ETIMEDOUT
03:11:48+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ node.list 78ms conn=63986452…22a1 id=8946fbb6…dabc
Log tail truncated (increase --max-bytes).
03:11:48+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channels resolved: 1465974811128758304/1498793521019224204 (guild:Broedkrummes server; channel:agenthub), 1465974811128758304/1498793490631491604 (guild:Broedkrummes server; channel:content)
03:11:48+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channels resolved: 1465974811128758304/1498793521019224204 (guild:Broedkrummes server; channel:agenthub), 1465974811128758304/1498793490631491604 (guild:Broedkrummes server; channel:content)
03:11:50+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord client initialized as 1472960908257923113 (Nova); awaiting gateway readiness
03:11:51+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} logged in to discord as 1498253644817236018 (Iris)
Gateway not reachable. Is it running and accessible?
Gateway target: ws://127.0.0.1:18888
02:57:17+00:00 error Health check failed: Error: gateway timeout after 3000ms
Gateway target: ws://127.0.0.1:18888
Source: local loopback
Config: /home/broedkrummen/.openclaw/openclaw.json
Bind: loopback

quick swallowBOT
#

Yep — this now sounds less like channel config and more like the Gateway process wedging / event loop not answering RPC.

A few notes:

  • Completion cache update failed: spawnSync /usr/bin/node ETIMEDOUT is probably not the Discord/Telegram root cause. That’s from update/doctor trying to refresh shell completions and timing out after ~30s.
  • The important part is: Health check failed: gateway timeout after 3000ms against ws://127.0.0.1:18888. If logs are still printing but health/RPC times out, the Gateway is likely alive but not responsive.
  • The Discord logs show two bot identities (Nova and Iris). If that’s intentional, fine. If not, check for duplicate/mixed Discord accounts/tokens — especially env fallback vs configured accounts.

Can you run these and attach/paste the safe outputs?

openclaw --version
openclaw gateway status --deep
openclaw health --verbose --timeout 15000
openclaw logs --limit 1000 --max-bytes 2000000 --plain
#

Best next step for a bug report:

openclaw gateway diagnostics export

That export is designed to be shareable/redacted. Please file it here: https://github.com/openclaw/openclaw/issues

If you need uptime meanwhile and this definitely started with 2026.4.25, a temporary rollback is reasonable:

openclaw update --tag 2026.4.24
openclaw doctor
openclaw gateway restart

Also mention in the issue whether Nova + Iris are intentionally both enabled. That detail may matter.

lunar cairn
#

broedkrummen@ubuntu-8gb-fsn1-1:~$ openclaw --version
openclaw gateway status --deep
openclaw health --verbose --timeout 15000
openclaw logs --limit 1000 --max-bytes 2000000 --plain
OpenClaw 2026.4.26 (be8c246)

🦞 OpenClaw 2026.4.26 (be8c246) — I've seen your commit messages. We'll work on that together.

│
â—‡
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-29.log
Command: /usr/bin/node /home/broedkrummen/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18888
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18888

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

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

Runtime: running (pid 134568, state active, sub running, last exit 0, reason 0)
Warm-up: launch agents can take a few seconds. Try again shortly.
Connectivity probe: failed
Probe target: ws://127.0.0.1:18888
timeout
Capability: unknown

Port 18888 is already in use.

  • pid 134568 broedkrummen: openclaw-gateway (127.0.0.1:18888)
  • Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
    Listening: 127.0.0.1:18888
    Troubles: run openclaw status
    Troubleshooting: https://docs.openclaw.ai/troubleshooting
#

it is intentional with multi bot setup

quick swallowBOT
#

That output is the smoking gun:

systemd says the Gateway process is running and owns port 18888, but the local WS/RPC probe times out. So this is not “Discord can’t connect” — the Gateway is wedged/unresponsive.

Also: “Port 18888 is already in use” is expected here because the stuck Gateway process owns it. Don’t switch ports yet.

Please run these separately and paste the output:

openclaw health --verbose --timeout 15000
openclaw logs --limit 1000 --max-bytes 2000000 --plain
openclaw gateway diagnostics export --json

If health hangs/fails again, try one clean restart and immediately check:

# 
openclaw gateway restart
sleep 20
openclaw gateway status --deep
openclaw health --verbose --timeout 15000

If it wedges again after restart, that’s likely a regression and the diagnostics zip is the best thing to attach to an issue: https://github.com/openclaw/openclaw/issues

Temporary uptime workaround:

openclaw update --tag 2026.4.24
openclaw doctor
openclaw gateway restart
#

The Completion cache update failed line is probably just update/doctor shell-completion refresh timing out — annoying, but not the main cause.

#

Got it — then the multi-bot part is probably a red herring. Thanks for confirming.

Focus on the Gateway wedge:

openclaw logs --limit 1000 --max-bytes 2000000 --plain
openclaw gateway diagnostics export --json

If the diagnostics command also times out, do this:

openclaw gateway restart
sleep 20
openclaw gateway diagnostics export --json
#

Attach the resulting zip to a GitHub issue and mention:

  • OpenClaw 2026.4.26 (be8c246)
  • Started after 2026.4.25
  • systemd process stays running, port 18888 owned by gateway
  • local WS/RPC probe times out
  • affects both Discord and Telegram
  • multi-bot Discord setup is intentional

That’s enough for maintainers to chase the regression.

lunar cairn
#

🦞 OpenClaw 2026.4.26 (be8c246) — Your terminal just grew claws—type something and let the bot pinch the busywork.

│
â—‡
Gateway connection:
Gateway target: ws://127.0.0.1:18888
Source: local loopback
Config: /home/broedkrummen/.openclaw/openclaw.json
Bind: loopback
Discord: configured
Telegram: configured
Agents: nova (default), iris, hemingway, archimedes
Heartbeat interval: 30m (nova), disabled (iris), disabled (hemingway), disabled (archimedes)
Session store (nova): /home/broedkrummen/.openclaw/agents/nova/sessions/sessions.json (6 entries)

  • agent:nova:discord:direct:1455735626665164871 (6m ago)
  • agent:nova:main (25m ago)
  • agent:nova:telegram:direct:7099985715 (25m ago)
  • agent:nova:discord:channel:1498259427055108136 (49m ago)
  • agent:nova:discord:channel:1474026544333717635 (50m ago)
    Session store (iris): /home/broedkrummen/.openclaw/agents/iris/sessions/sessions.json (4 entries)
  • agent:iris:discord:direct:1455735626665164871 (25m ago)
  • agent:iris:telegram:direct:7099985715 (28m ago)
  • agent:iris:discord:channel:1498793490631491604 (50m ago)
  • agent:iris:telegram:slash:7099985715 (70m ago)
    Session store (hemingway): /home/broedkrummen/.openclaw/agents/hemingway/sessions/sessions.json (4 entries)
  • agent:hemingway:discord:direct:1455735626665164871 (25m ago)
  • agent:hemingway:telegram:direct:7099985715 (28m ago)
  • agent:hemingway:discord:channel:1498793490631491604 (49m ago)
  • agent:hemingway:telegram:slash:7099985715 (411m ago)
    Session store (archimedes): /home/broedkrummen/.openclaw/agents/archimedes/sessions/sessions.json (3 entries)
  • agent:archimedes:discord:direct:1455735626665164871 (25m ago)
  • agent:archimedes:telegram:direct:7099985715 (27m ago)
  • agent:archimedes:telegram:slash:7099985715 (69m ago)

🦞 OpenClaw 2026.4.26 (be8c246) — If you're lost, run doctor; if you're brave, run prod; if you're wise, run tests.

│
â—‡
Gateway not reachable. Is it running and accessible?
Gateway target: ws://127.0.0.1:18888
Source: local loopback
Config: /home/broedkrummen/.openclaw/openclaw.json
Bind: loopback
Hint: run openclaw doctor.
{
"path": "/home/broedkrummen/.openclaw/logs/support/openclaw-diagnostics-2026-04-29T03-18-39-417Z-136754.zip",
"bytes": 31363,
"manifest": {
"version": 1,
"generatedAt": "2026-04-29T03:18:39.417Z",
"openclawVersion": "2026.4.26",
"platform": "linux",
"arch": "x64",
"node": "24.14.1",
"stateDir": "$OPENCLAW_STATE_DIR",
"contents": [
{
"path": "diagnostics.json",
"mediaType": "application/json",
"bytes": 1572
},
{
"path": "config/shape.json",
"mediaType": "application/json",
"bytes": 593
},
{
"path": "config/sanitized.json",
"mediaType": "application/json",
"bytes": 10804
},
{
"path": "logs/openclaw-sanitized.jsonl",
"mediaType": "application/x-ndjson",
"bytes": 197366
},
{
"path": "status/gateway-status.json",
"mediaType": "application/json",
"bytes": 4083
},
{
"path": "health/gateway-health.json",
"mediaType": "application/json",
"bytes": 7962
},
{
"path": "stability/latest.json",
"mediaType": "application/json",
"bytes": 506
},
{
"path": "summary.md",
"mediaType": "text/plain; charset=utf-8",
"bytes": 1470
}
],
"privacy": {
"payloadFree": true,
"rawLogsIncluded": false,
"notes": [
"Stability bundles are payload-free diagnostic snapshots.",
"Logs keep operational summaries and safe metadata fields; payload-like fields are omitted.",
"Status and health snapshots redact secrets, payload-like fields, and account/message identifiers.",
"Config output includes useful settings with credentials, private identifiers, and prompt text redacted."
]
}
}
}
broedkrummen@ubuntu-8gb-fsn1-1:~$

quick swallowBOT
#

Perfect, thanks — that confirms it’s intentional and gives a good bug artifact.

This is now clearly not a Discord/Telegram config issue. It’s a Gateway responsiveness regression: service is running, port is owned, diagnostics can read local files, but WS/RPC health can’t get an answer.

Please attach this zip to a GitHub issue:

/home/broedkrummen/.openclaw/logs/support/openclaw-diagnostics-2026-04-29T03-18-39-417Z-136754.zip

Issue link: https://github.com/openclaw/openclaw/issues

Suggested title:

Gateway wedges after 2026.4.25: systemd running but local WS/RPC health times out
#

Also: Node 24.14.1 looks fine — Node 24 is the recommended runtime, so I wouldn’t chase that.

For uptime, either rollback:

openclaw update --tag 2026.4.24
openclaw doctor
openclaw gateway restart

Or, if you’re willing to test unreleased fixes, try main:

openclaw update --tag main
openclaw doctor
openclaw gateway restart
#

If rollback fixes it, mention that in the issue — that’s very useful signal.

lunar cairn
#

broedkrummen@ubuntu-8gb-fsn1-1:~$ openclaw update --tag main
openclaw doctor
openclaw gateway restart
Updating OpenClaw...

│
â—‡ âś— Updating via package manager (76.79s)
npm error at Module._load (node:internal/modules/cjs/loader:1242:25)
npm error at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
npm error at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
npm error at node:internal/main/run_main_module:33:47 {
npm error code: 'MODULE_NOT_FOUND',
npm error requireStack: []
npm error }
npm error
npm error Node.js v24.14.1
npm error A complete log of this run can be found in: /home/broedkrummen/.npm/_logs/2026-04-29T03_21_46_237Z-debug-0.log
│
â—‡ âś— Retrying update without optional deps (71.3s)
npm error at Module._load (node:internal/modules/cjs/loader:1242:25)
npm error at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
npm error at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
npm error at node:internal/main/run_main_module:33:47 {
npm error code: 'MODULE_NOT_FOUND',
npm error requireStack: []
npm error }
npm error
npm error Node.js v24.14.1
npm error A complete log of this run can be found in: /home/broedkrummen/.npm/_logs/2026-04-29T03_23_03_069Z-debug-0.log

Update Result: ERROR
Root: /home/broedkrummen/.npm-global/lib/node_modules/openclaw
Reason: global update (omit optional)
Before: 2026.4.26
After: 2026.4.26

Total time: 148.57s

quick swallowBOT
#

That --tag main attempt failed before changing anything (Before/After both 2026.4.26), so no damage.

For testing main from an npm install, try the git/dev channel instead:

openclaw update --channel dev --dry-run
openclaw update --channel dev
openclaw doctor
openclaw gateway restart

If you just want uptime, I’d skip main and rollback:

openclaw update --tag 2026.4.24
openclaw doctor
# 
openclaw gateway restart

Also add this failed --tag main output to the GitHub issue. It’s a second useful bug signal: npm package-manager update to github:openclaw/openclaw#main is throwing MODULE_NOT_FOUND.

Docs: https://docs.openclaw.ai/install/updating

lunar cairn
#

Restarted systemd service: openclaw-gateway.service
broedkrummen@ubuntu-8gb-fsn1-1:~$ openclaw update --tag 2026.4.24
│
â—‡ Downgrading from 2026.4.26 to 2026.4.24 can break configuration. Continue?
│ Yes
Updating OpenClaw...

│
â—‡ âś“ Updating via package manager (35s)

Update Result: ERROR
Root: /home/broedkrummen/.npm-global/lib/node_modules/openclaw
Reason: global install verify
Before: 2026.4.26
After: 2026.4.26

Total time: 36.86s

quick swallowBOT
#

Okay, that downgrade also failed without changing the live install (After: 2026.4.26). The key bit is:

Reason: global install verify

So npm likely installed the staged 2026.4.24 package, but OpenClaw refused to swap it in because package verification failed.

Use the installer recovery path instead of openclaw update:

openclaw gateway stop

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh \
  | bash -s -- --install-method npm --version 2026.4.24 --no-onboard