Troubleshooting
Find the cause before changing the runtime.
Follow the evidence
Begin with doctor, then status, health and errors. A running container is not proof of broker readiness. Health separates MT5, Telegram and AI provider status. Degraded health returns exit code 1 as well as unhealthy state.
lvct doctor
lvct health
lvct errors --since 1hCommon causes
IPC/terminal errors: inspect sidecar logs and the broker server selection. Algo Trading errors: check terminal and broker permissions. Provider errors: check model, credentials and credit. Telegram FloodWait: respect its delay. Storage/decryption errors: check disk access and the original key; do not delete the database.
Critical error context
ERROR includes failures; CRITICAL/FATAL is a stricter filter. Traceback lines stay with the matching error. CLI failures are retained in a bounded private logs/cli.jsonl journal. If Docker is unavailable, errors still shows recent CLI failures. Do not blindly repeat an ambiguous broker action.
lvct logs --level critical --since 1d
lvct logs --service mt5-sidecar --level error --tail 300