Task 0.5 of clean-analyst-bootstrap. Greenfield rewrite — no fallback, no aliases. Existing dev environments lose their cached PAT and must re-authenticate. Env var renames (hard cutover): - DA_CONFIG_DIR -> AGNES_CONFIG_DIR - DA_SERVER -> AGNES_SERVER - DA_SERVER_URL -> AGNES_SERVER_URL (test-only stale ref, not in spec) - DA_NO_UPDATE_CHECK -> AGNES_NO_UPDATE_CHECK - DA_LOCAL_DIR -> AGNES_LOCAL_DIR - DA_TOKEN -> AGNES_TOKEN - DA_STREAM_RETRIES -> AGNES_STREAM_RETRIES Config dir rename: ~/.config/da/ -> ~/.config/agnes/ (across code, comments, docstrings, error messages, install templates, dev scripts). Stale `da X` references in CLI source (and adjacent app/, tests/): swept docstrings, comments, help text, and error messages where the verb survives the rewrite (init, pull, push, catalog, status, diagnose, auth, admin, skills, query, schema, describe, explore, disk-info, snapshot, login, logout, whoami, server, setup) and replaced `da X` with `agnes X`. Intentionally kept `da sync`, `da fetch`, `da analyst`, `da metrics` — those verbs are removed in later tasks; the legacy strings will be detected by `_LEGACY_STRINGS` (added in Task 2). Test fixes: - TestCLIVersion now asserts output starts with `agnes ` (was `da `). Test results: 2675 passed, 25 skipped (full pytest run, excluding 9 pre-existing test_db.py / test_user_management.py / test_e2e_extract.py / test_cli_binary_rename.py failures unrelated to this rename).
1.1 KiB
1.1 KiB
Troubleshoot — Diagnostic procedures
Quick Check
agnes diagnose --json
Common Issues
Data not updating
agnes diagnose --component data— check data freshnessagnes server logs scheduler --since 1h— check scheduler logs- Verify data source credentials:
agnes admin test-connection
Cannot login
- Check server is running:
curl http://server:8000/api/health - Check user exists:
agnes admin list-users(from admin account) - Re-generate token:
agnes login --email your@email.com
DuckDB errors locally
- Re-sync:
da sync(rebuilds views) - Check disk space:
du -sh user/duckdb/ - Delete and re-create:
rm user/duckdb/analytics.duckdb && da sync
Server unresponsive
docker compose ps— check container statusdocker compose logs app --tail 50— check app logsdocker compose restart app— restart app
Escalation
If automated diagnostics don't help:
- Collect full diagnostic:
agnes diagnose --json > /tmp/diag.json - Collect server logs:
docker compose logs > /tmp/logs.txt - Share both files with admin