Product

Logs & Debugging

Logs & Debugging

Where to find logs and how to use them when things go wrong.

Service Logs (systemd journal)

Both easyClaw and OpenClaw run as systemd services. Their logs go to the systemd journal.

OpenClaw Gateway

sudo journalctl -u openclaw-gateway -f

This shows gateway startup, channel connections (Telegram, Slack, Nostr, etc.), WebSocket activity, and errors.

Common things to look for:

• listening on — confirms the gateway started
• telegram connected / slack connected — channel status
• error / ECONNREFUSED — connection failures
• OOMKilled — ran out of memory (check swap with free -h)

easyClaw WebUI

sudo journalctl -u easyclaw-webui -f

This shows the web interface, login attempts, API calls, and service management actions.

Useful journalctl flags

• -f — follow (live tail)
• -n 100 — last 100 lines
• --since "1 hour ago" — filter by time
• --no-pager — dump all output without paging
• -p err — only errors

Example: Last 50 gateway errors:

sudo journalctl -u openclaw-gateway -p err -n 50 --no-pager

OpenClaw Runtime Logs

OpenClaw also writes its own log files:

/home/openclaw/.openclaw/logs/

These are the logs that appear in the Control Panel → Logs tab. They contain detailed session activity, tool calls, and model interactions.

nginx Access & Error Logs

sudo tail -f /var/log/nginx/access.log
sudo tail -f /var/log/nginx/error.log

Useful for debugging SSL, proxy, and routing issues.

Quick Diagnostics

Check if services are running

sudo systemctl status openclaw-gateway
sudo systemctl status easyclaw-webui

Check memory usage

free -h

If you see very low free/available memory and high swap usage, your VPS may need more RAM or a larger swap file (configurable in Settings).

Check disk space

df -h /

Restart services

sudo systemctl restart openclaw-gateway
sudo systemctl restart easyclaw-webui

Nuclear option — restart both

sudo systemctl restart openclaw-gateway && sudo systemctl restart easyclaw-webui

Common Issues in Logs

Log Message	Meaning	Fix
ECONNREFUSED 127.0.0.1:18789	Gateway not running	sudo systemctl start openclaw-gateway
OOMKilled	Out of memory	Increase swap in Settings, or upgrade VPS
ENOSPC	Disk full	Clean up /home/openclaw/.openclaw/logs/
EACCES	Permission denied	sudo chown -R openclaw:openclaw /home/openclaw/.openclaw/
ERR_TLS_CERT_ALTNAME_INVALID	SSL cert mismatch	Re-run SSL setup from Settings
rate limit	API provider throttling	Wait and retry, or switch models

Getting Help

If you can’t resolve an issue:

1. Copy the relevant log output
2. Enable support access from 🔒 Security
3. Email support@easynode.ai with the logs