メニュー
Diagnose and fix OpenClaw sentinel service issues on ubuntu24, especially Feishu connection failures, env config drift, and startup delays.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
macOS-specific automation: iMessage/SMS messaging and desktop control (screenshots, clicks, keyboard input).
Messaging platform integrations: email (IMAP/SMTP via Himalaya), X/Twitter (xurl CLI), and Yuanbao groups (@mentions, DMs).
Control creative software programmatically: ComfyUI (AI image/video generation via REST/WebSocket API) and TouchDesigner (real-time visual programming via MCP).
Systematic engineering disciplines: debugging (root cause investigation), TDD (test-first development), and exploratory QA (web app testing).
Creative coding: p5.js sketches, Manim animations, Pretext text layouts.
Create, read, edit .pptx decks, slides, notes, templates.
SOC 職業分類に基づく
| name | openclaw-sentinel-troubleshooting |
| category | devops |
| description | Diagnose and fix OpenClaw sentinel service issues on ubuntu24, especially Feishu connection failures, env config drift, and startup delays. |
Use when OpenClaw sentinel (openclaw.service) fails to start, crashes, or cannot connect to Feishu after a system restart or deployment on ubuntu24.
systemctl status openclaw.service/opt/openclaw//opt/openclaw-team/.env/opt/openclaw-team//www/server/nodejs/v24.14.0/bin/nodesystem busy / 400 Bad Request)Symptoms:
code: 1000040346, system busy in logsGET /open-apis/bot/v3/info returns 400Root Cause (Historical): FEISHU_SENTINEL_APP_ID and FEISHU_SENTINEL_APP_SECRET in /opt/openclaw-team/.env were overwritten with placeholder values (cli_xxxx, ***) during a config update or git pull.
Verification:
ssh root@ubuntu24 "grep FEISHU_SENTINEL_APP /opt/openclaw-team/.env"
# Expected: real values like cli_a92682269af8dbdf, NOT cli_xxxx
Fix:
/opt/openclaw-team/.envssh root@ubuntu24 "systemctl restart openclaw"ssh root@ubuntu24 "journalctl -u openclaw -n 50 --no-pager | grep -E 'ws client ready|bot identity'"Symptoms: Service shows active (running) but port 18789 is not bound.
Cause: --force flag in systemd service triggers full rebuild/npm install. Takes 30-60 seconds.
Fix: Wait 60s, then check: ss -tlnp | grep 18789
Sentinel was historically left running for months (PID unchanged since March). System restarts force re-read of .env, exposing stale/placeholder configs. Always verify .env after restarts.