EdgeClaw Operations Runbook

Server: 64.181.198.130 | User: ubuntu | Domain: edge-assist.duckdns.org

Checking If Everything Is Running

See all running services:

systemctl --user list-units --type=service --state=running

You should see 12 services (ignore dbus). If something is missing, it crashed — restart it.

Health check (EdgeClaw itself):

curl -s http://localhost:8080/health | python3 -m json.tool

If this fails, EdgeClaw is down. Restart it (see below).

Dashboard: https://edge-assist.duckdns.org/data-status

• Green = fresh data, working fine
• Yellow = stale, might need attention
• Red = broken, something stopped updating

All 13 Services

Restarting Things

Restart one service:

systemctl --user restart <service-name>

Example: systemctl --user restart claude-bridge

Restart EdgeClaw only:

systemctl --user restart edgeclaw

WARNING: This resets all internal scheduled jobs (scrapers, edge scanner, etc.). They have a recovery system that re-runs missed jobs 30 seconds after startup, BUT if EdgeClaw restarts several times in a row (like during the 5-7 AM window), the recovery may not catch everything. The 8 AM props scraper has been missed before because of this.

Restart all Telegram and Discord bots:

for s in claude-bridge claude-techsupport claude-analyst claude-wiped claude-opusgod discord-edge discord-analyst discord-techsupport; do systemctl --user restart $s; done

Restart everything (nuclear option):

systemctl --user restart edgeclaw ta-models openclaw-gateway
for s in claude-bridge claude-techsupport claude-analyst claude-wiped claude-opusgod discord-edge discord-analyst discord-techsupport; do systemctl --user restart $s; done

Checking Logs

EdgeClaw logs (last 50 lines):

journalctl --user -u edgeclaw --no-pager -n 50

Any bot's logs:

journalctl --user -u claude-bridge --no-pager -n 50

Replace claude-bridge with whatever service you want.

Settlement logs: data/logs/settlement-cron.log Pinnacle accuracy logs: logs/pinnacle-accuracy.log

To read a log file, ask Claude Code: "show me the last 30 lines of settlement-cron.log"

System Crontab (runs on its own, not inside EdgeClaw)

These survive EdgeClaw restarts. They run no matter what.

All times are ET.

EdgeClaw Internal Scheduled Jobs

These run INSIDE EdgeClaw and restart when EdgeClaw restarts. They include scrapers, edge scanner runs, and other data collection. See the warning above about missed runs after restarts.

Settlement was moved OUT of EdgeClaw's internal scheduler to the system crontab (above) specifically to avoid the missed-run problem.

Settlement Operations

Automatic schedule:

• 3 AM: ESPN settlement
• 4:05 AM: BBRef settlement
• 8 AM, 2 PM, 8 PM: Regular settlement runs

Run settlements manually: Ask Claude Code "run settlements manually"

Check what hasn't settled yet: Ask Claude Code: "show me unsettled props" or "query player_prop_edges where actual_outcome is null"

Edge Scanner

Automatic: Runs at 8 AM, 10 AM, 2 PM, 6 PM, plus closing times (all inside EdgeClaw).

Manual trigger: Ask Claude Code "run the edge scanner"

View results: Dashboard at /data-status/view/edge-scanner-nba (and similar paths for other sports)

Scraper Troubleshooting

1. Check the dashboard — red or yellow means something is stale
2. Check EdgeClaw logs for errors
3. Most common fix: restart EdgeClaw (systemctl --user restart edgeclaw)
4. If one specific scraper keeps failing, the source website probably changed its layout. Ask Claude Code to look at the scraper code and the error.

Data Cleanup

All data lives in SQLite databases inside data/db/. Never edit these files directly.

Always look before you delete. Ask Claude Code:

• "show me rows from [table] where [condition]" — to preview
• "delete rows from [table] where [condition]" — to remove

Common examples:

• "delete test data from player_prop_edges"
• "delete edge scanner results older than 30 days"
• "show me rows from audit_log where cost_estimate is null"

Databases

All in /home/ubuntu/edgeclaw/data/db/:

Rollback (Undoing Changes)

See recent code changes:

git log --oneline -10

Undo a specific change:

git revert <commit-hash>

Or just ask Claude Code:

• "undo the last change"
• "rollback to before [describe what changed]"

Quick Reference