---
name: arcana-remote
description: "vvv-bots scheduler log is fetched from arcana over SSH; the host is `ubuntu@100.125.166.65`"
metadata:
node_type: memory
type: reference
originSessionId: 71d40fa2-b151-4c81-9821-f0dfeb7a0f66
---

The vvv-bots scheduler log lives at
`/home/ubuntu/workspace/web/vvv-bots/logs/scheduler.log` on **arcana**
(`ubuntu@100.125.166.65`). Shadow's monitor pulls it via
`ssh -o StrictHostKeyChecking=no -o ConnectTimeout=10 ubuntu@arcana
tail -100 `. Key-based auth is already set up.

When debugging the daily report on shadow:
- "SSH failed" in `daily_report.log` → arcana side (tailscale down,
scheduler crashed, log file moved).
- "Ollama接続失敗" → shadow side (see [[monitor-model-mismatch]]).
- Empty Discord message → check `summarize_logs.py` output manually with
`python3 ai-agents/monitor/summarize_logs.py`.