Cause (Documented platform behavior): The Ollama server wraps HTTP failures to its runner subprocess into this generic message, appending the runner last error when available; root causes vary (out of memory, GPU driver errors, model incompatibility).
Fix status: documented_behavior
Limitations:
- Generic surface error with multiple root causes; this record documents only the wrapping behavior.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/ollama/ollama/16b4376aeadbec58a18b9817d49c37b1b64e33d0/llm/llama_server.go (official_docs, unknown, documented_behavior): On completion request transport errors (not context cancel), returns "model runner has unexpectedly stopped..." with the runner last error message appended if present.
Search phrasings: ollama model runner has unexpectedly stopped; ollama runner stopped resource limitations; ollama 500 runner crash check server logs
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Requests fail with a generic runner-stopped error; the real cause (OOM, CUDA error, unsupported arch) is only in the server log.
- Context
- Product: Ollama Component: llm llama_server client Operation: POST /api/chat|generate|embed after model load, especially large context or GPU memory pressure Affected versions: unknown Environment: unknown HTTP status: 500 Packages: ollama source checked at main (see SHA) Trigger: The llama-server subprocess crashed or became unreachable during a completion request.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- model runner has unexpectedly stopped, this may be due to resource limitations or an internal error, check ollama server logs for details
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Ollama] "model runner has unexpectedly stopped, this may be due to resource limitations or an internal error, check ollama server logs for details"
Recommended action: Read the Ollama server log for the runner error preceding this message; reduce num_ctx/num_parallel or model size, update drivers/Ollama, or re-pull the model.
Option: Inspect server logs and reduce resource use [evidence: documented_workaround]
Applies when: Runner crash on load/inference
Steps:
1. journalctl -u ollama / server.log
2. Lower num_ctx or OLLAMA_NUM_PARALLEL
3. Update Ollama and GPU drivers
Expected: Runner stays up
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- e6c3dc98-bbe3-4d2f-b3ff-61d43594f2b9
- Proposed action
- Recommended action: Read the Ollama server log for the runner error preceding this message; reduce num_ctx/num_parallel or model size, update drivers/Ollama, or re-pull the model. Option: Inspect server logs and reduce resource use [evidence: documented_workaround] Applies when: Runner crash on load/inference Steps: 1. journalctl -u ollama / server.log 2. Lower num_ctx or OLLAMA_NUM_PARALLEL 3. Update Ollama and GPU drivers Expected: Runner stays up
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.