Skip to content

Troubleshooting

Symptom: SSH to VM times out, dashboard shows VM as down.

Check:

  1. Is UTM running? pgrep -f UTM
  2. Is bridge100 configured? ifconfig bridge100
  3. Can you ping the VM? ping 10.10.10.10

Fix:

Terminal window
# Restart UTM autostart (reconfigures bridge100)
launchctl bootout gui/$(id -u)/com.user.utm-autostart
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.user.utm-autostart.plist

Symptom: Health check shows a service as failed.

Quick fix:

Terminal window
bash ~/Projects/openclaw-skills/service-doctor/scripts/service-doctor.sh --fix

Symptom: launchctl list <label> returns “Could not find service.”

Fix:

Terminal window
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/<label>.plist

Check plist validity:

Terminal window
plutil -lint ~/Library/LaunchAgents/<label>.plist

Symptom: Gateway logs show 401 Unauthorized.

Fix: Rotate the affected token:

Terminal window
bash ~/Backups/rotate-secrets.sh

Or for just the gateway token:

Terminal window
openclaw setup-token

The JSON cache may be stale. Force regeneration:

Terminal window
touch ~/.sanctum/instance.yaml
# Next config read will regenerate the cache
  1. Check if the backend is running: curl http://localhost:3002/api/health/status
  2. Check the LaunchAgent: launchctl list com.manoir.command-center
  3. Check port 3001: lsof -i :3001

If the watchdog keeps alerting for a known-down service:

Terminal window
# Check dedup state
cat ~/.sanctum/.watchdog-state
# Clear state to reset dedup
rm ~/.sanctum/.watchdog-state