2026 OpenClaw 무응답·무소음 실패: heartbeat, thinking, Cron, 채널

대시보드와 18789 포트는 통과했지만 오래 침묵, Cron 후 배달 없음, 로그는 성공인데 채팅 비어 있음이 보이면 세 가지를 먼저 분리하세요: thinking/heartbeat 빈 출력, 가짜 워크플로 경로, 채널/Webhook vs 설치 문제. 분류표와 5단계(doctor, models status, logs), 재설치를 미루는 경우를 정리했습니다. 공통 오류, sessions_spawn, Webhook과 함께 읽으세요.

Troubleshooting OpenClaw no-reply and silent Cron on Mac cloud

목차

1. 무응답이 곧 게이트웨이 다운은 아님

The path is long: channel ingress → gateway → model → tools/workflows → channel egress. Any hop can yield no stack trace and no visible text, which users call "no reply." That differs from install-time failures with clear exit codes. This article assumes you can reach the admin plane; if 18789 is still blocked, return to first deploy and firewall.

  1. Thinking mode and heartbeat jobs: Some models stay inside "thinking" for scheduled jobs and end with empty deliverable text, so channels have nothing to send. A common mitigation is disabling thinking or capping reasoning budget on Cron/heartbeat paths. If chat works but schedules never speak, check this before reinstalling packages.
  2. Phantom workflow files: Models may reference non-existent files like WORKFLOW_AUTO.md. If automation tries to read them, you get silent no-ops. Fix with real repo files and prompt constraints, plus cwd and sandbox alignment.
  3. Channel delivery: Gateway logs "handled" while Telegram/Slack shows nothing due to 429s, bad Webhook URLs, or muted bots—model-agnostic but often blamed on OpenClaw. Use curl probes and launchd env.

False silences also come from clients collapsing long messages or stale UI caches while the server returned 200—correlate logs with HTTP status and correlation IDs. Queues: duplicate Webhooks or dedup rules can drop jobs quietly; enable queue-depth debug logging and verify token and rate limits.

2. 증상 매트릭스

What you seeSuspect layerVerify firstUsually not first
Everything silent, doctor yellowProvider keys / routingopenclaw models status, minimal chat turnPort 18789 if HTTP health OK
Only Cron/heartbeat silentthinking config / timeoutsDisable thinking on schedule path; log durationFull reinstall
Logs OK, IM emptyChannel token / Webhook / 429curl Webhook, bot permissionsModel temperature
Sometimes empty after "success"cwd, sandbox, phantom pathsMinimal script, fixed cwdRandom hardware
After upgradeConfig migrationUpgrade notes and OPENCLAW_* diffDisk failure

Prefix tickets with one matrix row (e.g. "Cron-only + thinking suspect") to shorten handoffs. Note which channel reproduces when you run many IM integrations.

3. 5단계 진단 경로

  1. Baseline: openclaw doctor and openclaw health --json if available; align Node major with quick deploy docs.
  2. Models: openclaw models status; A/B with a known-good model on silent tasks.
  3. Logs: openclaw logs --follow; trace inbound event to outbound send. If inference stops with no send, revisit thinking/heartbeat.
  4. Channel probe: smallest echo through the same channel; failures often mean env vars missing from launchd (not inherited from .zshrc).
  5. Minimal config: staging with one channel, one model, tools off; merge deltas instead of nuking the install.
launchctl asuser $(id -u) sudo -u $(whoami) env | egrep 'OPENCLAW|PATH|NODE'
Note: launchd-managed gateways do not see exports defined only in interactive shells—classic "SSH manual start works, reboot silent."

Add a timebox to runbooks: first 15 minutes only channel probe + models status; avoid changing three unrelated knobs at once. Only then consider rollback or clean-dir reinstall with tarball evidence.

4. 파라미터·타임아웃·운영 메모

Heartbeat agents: disable thinking or cap steps for short cadence jobs (key names vary by version—diff after upgrades). Match client, model, and channel timeouts; log backoff for 429/5xx or the UI stays quiet. Watch disk and log rotation—full volumes mimic silence. NTP skew can cause intermittent JWT/Webhook 401s; check time on Mac cloud nodes. Some channels truncate Unicode or large payloads; compare raw outbound logs. Avoid printing full secrets in logs; use short-lived read-only tokens for triage.

5. 재설치 루프에서 재현 가능한 Mac 클라우드 기반으로

Reinstalling globally on every silence hides real causes—especially when laptops and cloud nodes diverge on keys and plist env.

Prefer a written layered matrix and five-step playbook. For long-running multi-channel automation, renting VPSMAC M4 Mac cloud with a silent-failure checklist in the handover usually beats cycling containers: unified logs, clear service user, native macOS next to Apple toolchains.

6. FAQ

Cron silent but chat works?

Check thinking/heartbeat settings and scheduled user env, then timeouts and channel-side drops.

No errors in logs—success?

Not until you see outbound delivery or channel ACK.

When to reinstall?

When doctor shows corrupted install, Node ABI mismatch, or upstream requires clean dir—otherwise triage first.

How does this relate to the common-errors article?

Use common errors for install/port/TLS; this article covers weak-signal silence.