# 2026-04-01 — Daily Notes

## 23:10 UTC — Heartbeat Check

### Systems Status
- Disk (/): OK — 59% used (966G/1.7T)
- Memory: OK — 17Gi/62Gi (27%) used, 44Gi available
- Swap: Watch — 17Gi/33Gi used (~52%)
- Load: OK — 3.06 / 3.04 / 2.84
- lshttpd: Active
- MySQL: Active
- Redis: Active
- OpenClaw Gateway (core): Running, API operational
- OpenClaw Gateway (Signal): DOWN — crash-looping

### Signal Channel Issue
- signal-cli subprocess crashing: "User +4915223016139 is not registered"
- Auto-restart attempt 7/10, 300s backoff — will exhaust retries soon
- Needs: Signal re-registration for +4915223016139
- Could not alert main session (sandbox restriction)

## 23:36 UTC — Heartbeat Check (Cron)

### Systems Status
- Disk: 59% — OK
- Memory: 17Gi/62Gi (27%) — OK
- Swap: 52% — Stable
- Load: 5.29 — OK (deutlich besser als letzte Tage)
- lshttpd: Active
- MariaDB: Active
- Redis: Active
- OpenClaw Gateway (core): Running (pid 921655)

### Signal Channel — STILL DOWN ⚠️
- Crash-loop continues: attempt 8/10, 300s backoff
- Error: "User +4915223016139 is not registered"
- **Needs: Signal re-registration**
- Attempted to alert main session → sandbox restriction blocked delivery

### Other Observations
- xmlrpc.php hit still running (known, Wächter-aware)
- litellm consuming 88% CPU (crash-looping as usual)
- ffmpeg no longer in top processes — may have completed

### Mission Control / HostBill
- No MC database found in sandbox
- HostBill not accessible from sandbox (TLS)
- Last known state (21:34 UTC): 0 open tasks

### Verdict
Core services healthy. Only actionable issue is Signal channel (needs re-registration). Cannot escalate from sandbox — next non-sandbox heartbeat or main session should pick this up.