Runtime problems
warning
Runtime problems
State machine reminder
STOPPED → STARTING → READY / FAILED. A running PID alone is not READY — the API must answer. Details: Runtime.
Won't start
| Symptom | Fix |
|---|---|
| Exits immediately | Reinstall runtime: botconnector runtime install |
| Missing DLL / 0xc000007b | Platform mismatch — reinstall the correct package |
| Blocked by antivirus | Whitelist the runtime path; see Download signing note |
| Port already in use | botconnector ps → stop stale instance, or --port |
Crashes under load
- OOM during generation (context grew) → lower context or smaller quant: Memory problems.
- GPU backend crash → fall back to CPU to confirm the model itself is fine, then debug the backend: GPU problems.
Never becomes READY
botconnector runtime status— note the state.- Read the newest log in
%USERPROFILE%\botconnector\logs. - Test the API directly:
curl http://127.0.0.1:11435/v1/models. - Restart cleanly:
botconnector server stopthenserver start.
Reporting
Include: doctor --json output, runtime status --json, the log file, model id + quantization, backend and OS build. See Runtime troubleshooting.