openclaw - 💡(How to fix) Fix [Bug]: Discord Channel Flapping [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74044Fetched 2026-04-30 06:29:25
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
commented ×2cross-referenced ×1labeled ×1mentioned ×1

Discord provider on Raspberry Pi arm64 causes gateway to wedge at ~100% CPU after startup on OpenClaw 2026.4.26. Gateway is healthy when channels.discord.enabled=false.

Root Cause

Discord provider on Raspberry Pi arm64 causes gateway to wedge at ~100% CPU after startup on OpenClaw 2026.4.26. Gateway is healthy when channels.discord.enabled=false.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Discord provider on Raspberry Pi arm64 causes gateway to wedge at ~100% CPU after startup on OpenClaw 2026.4.26. Gateway is healthy when channels.discord.enabled=false.

Steps to reproduce

  1. Run OpenClaw 2026.4.26 (be8c246) on Raspberry Pi arm64 with Node 22.22.2.
  2. Enable Discord channel with a valid bot token.
  3. Start/restart the gateway via systemd user service.
  4. Wait for gateway startup.
  5. Observe logs around:
  • [gateway] ready
  • [discord] [default] starting provider
  1. Run:
  • openclaw gateway status --deep
  • ps -o pid,etime,%cpu,%mem,rss,cmd -p <gateway_pid>
  1. Disable Discord:
  • openclaw config set channels.discord.enabled false --strict-json
  • openclaw gateway restart
  1. Observe gateway becomes responsive again.

Expected behavior

Discord provider should start, log in, keep gateway responsive, and allow openclaw gateway status --deep / openclaw channels status --probe to complete normally.

Actual behavior

Gateway starts and listens on 127.0.0.1:18789, but after Discord provider startup it becomes unresponsive. CLI probes time out, WebSocket connections close with 1006, and openclaw-gateway spins around 100% CPU. With Discord disabled, gateway reports Connectivity probe: ok and Capability: admin-capable. Useful log snippets to include:

[gateway] ready [discord] [default] starting provider [ws] closed before connect ... code=1006

and if you have it:

[discord] channel resolve failed; using config entries. fetch failed | write EPIPE [discord] logged in to discord as ...

OpenClaw version

2026.4.26 (be8c246)

Operating system

Debian GNU/Linux 13.4 (trixie)

Install method

No response

Model

openrouter/minimax/minimax-m2.7

Provider / routing chain

openclaw>openrouter>minimax

Additional provider/model setup details

OpenClaw 2026.4.26 (be8c246) Raspberry Pi arm64, Node 22.22.2 service is correctly under /home/openclaw, direct Node ExecStart is normal gateway healthy with channels.discord.enabled=false gateway wedges at ~100% CPU after [discord] [default] starting provider previous log included write EPIPE during Discord channel resolve and sometimes eventually login skill-workshop disabled did not resolve it

Logs, screenshots, and evidence

Impact and severity

affected channels connectivity

Additional information

No response

extent analysis

TL;DR

The Discord provider on Raspberry Pi arm64 causes the OpenClaw gateway to become unresponsive and consume 100% CPU after startup, which can be temporarily mitigated by disabling the Discord channel.

Guidance

  • Verify that the issue is specific to the Discord provider by checking the logs for any errors or warnings related to the Discord channel, such as "write EPIPE" or "channel resolve failed".
  • Try disabling the Discord channel and restarting the gateway to confirm that it becomes responsive again.
  • Check the Node version and OpenClaw version for any known issues or compatibility problems.
  • Investigate the possibility of a resource constraint or dependency issue on the Raspberry Pi arm64 platform.

Example

No specific code snippet is available, but the issue can be reproduced by running the commands provided in the "Steps to reproduce" section.

Notes

The issue seems to be specific to the Discord provider on Raspberry Pi arm64, and the cause is unclear. Further investigation is needed to determine the root cause and develop a permanent fix.

Recommendation

Apply workaround: disable the Discord channel until a permanent fix is available, as it allows the gateway to become responsive again.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Discord provider should start, log in, keep gateway responsive, and allow openclaw gateway status --deep / openclaw channels status --probe to complete normally.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Discord Channel Flapping [2 comments, 2 participants]