Discord 只发不收排障:Raspberry Pi 上从 intents 到会话生成的逐层回归
场景:Discord bot 可发送但收不到消息、无 MESSAGE_CREATE、无新会话。前置:Pi/ARM64 环境可访问日志,且 bot intents 已配置。步骤:先验证连接与发送能力,再验证 read API 与 session 生成链路,最后做版本与状态清理回归。关键命令:systemctl status、sessions_list。验证:用户消息可触发会话并回复。风险:误判为 token 问题导致反复重建 bot。
GITHUBDiscovered 2026-02-15Author amr05008
Prerequisites
- Discord bot token is valid and required intents (including Message Content) are enabled in portal.
- You can run diagnostics on Raspberry Pi host and inspect gateway service logs.
Steps
- Confirm bot login and outbound send path first (service status + send test).
- Use message-read path to verify inbound messages are visible at API layer.
- Check whether group sessions are created after inbound messages; if zero, focus on event handler path.
- Restart gateway, clear stale state/cache carefully, and retest with a fresh mention message.
- Only then consider bot recreation/version upgrade as last resort.
Commands
systemctl --user status openclaw-gatewayopenclaw gateway restartopenclaw gateway statusVerify
A user mention triggers MESSAGE_CREATE handling and creates a live group session with reply.
Caveats
- Do not over-clean runtime state without backups; excessive cleanup can remove useful diagnostics.
- ARM64-specific runtime/event differences may require version-specific fixes(需验证).
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗