Summary: When Ollama fails to pull a model, stays on CPU after a suspend, or returns 404 / 429 / 503 from the local API, start with the official logs, then match the symptom to the GPU discovery and queue docs. This guide walks through Mac / Linux / Windows log paths, NVIDIA UVM reloads, AMD ROCm 7 discovery timeouts, common HTTP status codes, and the OLLAMA_MAX_QUEUE / parallel env vars — all checked against docs.ollama.com on 2026-11-07.
What “Ollama not working” usually means
Ollama is a local (and optionally cloud) runner for open models. The Mac and Windows apps auto-update; Linux reinstalls with the install script. The local server listens on 127.0.0.1:11434 by default. Most “not working” reports fall into four buckets: the process is running but logs show a GPU discovery failure, ollama pull cannot finish, the HTTP API returns an error status, or the model loads on CPU when you expected GPU.
This post is about the runner itself — install, GPU, pull, and API — not about wrapping UIs. If your chat UI cannot reach embeddings or a model path, also read our AnythingLLM troubleshooting post, which treats Ollama as a dependency.
Step 1: Read the logs before guessing
Official troubleshooting docs say the fastest path is the server log. Paths differ by platform:
- macOS:
cat ~/.ollama/logs/server.log - Linux (systemd):
journalctl -u ollama --no-pager --follow --pager-end - Docker:
docker logs <container-name>(usedocker psto find the name). Logs go to stdout/stderr inside the container. - Manual
ollama serve: logs stay in that terminal session. - Windows: Win+R →
explorer %LOCALAPPDATA%\Ollama. Latest log isserver.log; older rotations areserver-#.log. Binaries live under%LOCALAPPDATA%\Programs\Ollama; models and config under%HOMEPATH%\.ollama.
For extra debug output on Windows, quit the tray app, then in PowerShell set $env:OLLAMA_DEBUG="1" and launch ollama app.exe. On Linux/macOS, OLLAMA_DEBUG=1 increases GPU discovery detail. Join Discord only after you have a concrete log line — the docs explicitly recommend that for interpreting obscure messages.
Model storage locations (useful when a pull “succeeds” but the app cannot find weights): macOS ~/.ollama/models, Linux /usr/share/ollama/.ollama/models, Windows C:\Users\%username%\.ollama\models. Override with OLLAMA_MODELS; on the standard Linux installer the ollama user must own that directory.
Step 2: Fix pull and proxy failures
Pulls use HTTPS to fetch model layers. If you sit behind a corporate proxy, set HTTPS_PROXY (and install the proxy CA as a system certificate). The FAQ warns not to set HTTP_PROXY for Ollama — pulls are HTTPS-only, and an HTTP proxy setting can interrupt client connections to the local server.
In Docker, pass -e HTTPS_PROXY=https://proxy.example.com, or configure the Docker daemon proxy. Self-signed CAs may need a custom image that runs update-ca-certificates.
On Windows 10 WSL2, slow networking can stall both the installer and model downloads. The FAQ workaround: open the vEthernet (WSL) adapter properties → Configure → Advanced, and disable Large Send Offload Version 2 (IPv4) and (IPv6).
If Linux installs are broken on a bad release, pin a known version with the install script: curl -fsSL https://ollama.com/install.sh | OLLAMA_VERSION=0.5.7 sh (replace with the version you need). For tmp mounts with noexec, set OLLAMA_TMPDIR to a writable path such as /usr/share/ollama/.
Private or pushed models need your Ollama public key (macOS ~/.ollama/id_ed25519.pub, Linux under /usr/share/ollama/.ollama/, Windows under your user .ollama folder). Sign in via the app Settings, ollama signin, or paste the key at ollama.com/settings/keys.
Step 3: NVIDIA GPU discovery (driver 550+, UVM after suspend)
Hardware docs: Ollama supports NVIDIA GPUs with compute capability 5.0+ and driver 550+. Cards in the 5.0–6.2 compute range need driver 570+. Check your card on NVIDIA’s CUDA GPUs list before chasing software bugs.
On startup Ollama inventories GPUs and VRAM. When discovery fails, Linux logs often show CUDA-ish codes such as 3 (not initialized), 46 (device unavailable), 100 (no device), or 999 (unknown). Work through the official checklist:
- If you use Docker, confirm the NVIDIA container runtime:
docker run --gpus all ubuntu nvidia-smi. If that fails, Ollama cannot see the GPU either. - Load UVM:
sudo nvidia-modprobe -u. - Reload after flaky state:
sudo rmmod nvidia_uvmthensudo modprobe nvidia_uvm. - Reboot, then confirm you are on a current driver.
Linux suspend/resume: after sleep, Ollama sometimes fails NVIDIA discovery and falls back to CPU. The documented workaround for that driver bug is the same UVM reload: sudo rmmod nvidia_uvm && sudo modprobe nvidia_uvm.
If Docker initially uses the GPU then later drops to CPU with discovery errors, disable systemd cgroup management in Docker by adding "exec-opts": ["native.cgroupdriver=cgroupfs"] to /etc/docker/daemon.json on the host.
To limit which GPUs Ollama sees, set CUDA_VISIBLE_DEVICES to a comma-separated list of IDs (prefer UUIDs from nvidia-smi -L). An invalid ID such as -1 forces CPU. For deeper CUDA diagnostics, set CUDA_ERROR_LEVEL=50 and inspect dmesg for nvrm / nvidia lines.
Confirm placement with ollama ps. The Processor column shows 100% GPU, 100% CPU, or a split such as 48%/52% CPU/GPU.
Step 4: AMD ROCm 7 timeout and permissions
On Linux, AMD access usually needs video and/or render group membership for /dev/kfd. Wrong permissions produce a clear server-log error. In containers, pass numeric group IDs from ls -lnd /dev/kfd /dev/dri /dev/dri/* via extra --group-add flags.
If Linux discovery fails with messages like failed to finish discovery before timeout and a ~30s bootstrap duration, the system AMD driver is often too old. Ollama bundles ROCm 7 libraries that need a matching ROCm 7 kernel driver; ROCm 6.x or older can hang during discovery until timeout, then fall back to CPU. Upgrade with AMD’s amdgpu-install utility, reboot, and restart Ollama.
Useful env flags while debugging: AMD_LOG_LEVEL=3, OLLAMA_DEBUG=1, plus dmesg greps for amdgpu and kfd. Select a subset of AMD GPUs with ROCR_VISIBLE_DEVICES (prefer Uuid from rocminfo). Unsupported GFX targets can sometimes be forced with HSA_OVERRIDE_GFX_VERSION (for example 10.3.0) — treat that as experimental and match the closest supported LLVM target from the GPU docs table.
Windows AMD support requires an AMD ROCm v7 / HIP7-capable driver stack; the hardware page lists the RX 7000-class and PRO cards currently covered. Metal covers Apple GPUs. Extra Windows/Linux GPUs may appear via Vulkan (GGML_VK_VISIBLE_DEVICES; disable with OLLAMA_VULKAN=0 or device -1).
Step 5: API errors — 404, 429, 503 queue, 502 cloud
The API errors page documents standard HTTP statuses:
- 200 — success
- 400 — bad request (missing parameters, invalid JSON)
- 404 — not found (often “model doesn’t exist” — pull or name the tag correctly)
- 429 — too many requests / rate limit exceeded
- 500 — internal server error
- 502 — bad gateway (example given: cloud model cannot be reached)
Bodies are JSON: {"error":"..."}. Mid-stream failures arrive as an NDJSON object with an error property without changing the already-started status code.
Separately, the FAQ states that when too many requests hit the server it responds with 503 (overloaded). Raise capacity with OLLAMA_MAX_QUEUE (default 512). Related concurrency knobs:
OLLAMA_MAX_LOADED_MODELS— default 3 × GPU count (or 3 on CPU)OLLAMA_NUM_PARALLEL— parallel requests per model (default 1); RAM scales by parallel × context lengthOLLAMA_CONTEXT_LENGTH— default context is 4096 tokens unless overridden
How to set env vars: macOS app → launchctl setenv NAME value then restart the app; Linux systemd → systemctl edit ollama.service with Environment="NAME=value", then daemon-reload and restart; Windows → quit the tray app, edit user environment variables, relaunch from the Start menu.
Default keep-alive is five minutes. Unload with ollama stop MODEL, or pass API keep_alive as a duration, seconds, -1 (forever), or 0 (unload after the response). Server-wide default: OLLAMA_KEEP_ALIVE.
If autodetection picks a bad LLM library (crashes, wrong CPU path), force one with OLLAMA_LLM_LIBRARY (for example cpu_avx2). Server logs list available libraries such as cuda_v11, rocm_v6, cpu_avx2.
Ollama vs LM Studio vs Open WebUI
These three tools often appear in the same “local LLM” search results but solve different layers. Prices below are omitted on purpose — roles matter more for troubleshooting, and each product’s paid surface changes on its own site.
| Role | Ollama | LM Studio | Open WebUI |
|---|---|---|---|
| What it is | Local model server + CLI (+ optional Ollama cloud) | Desktop app focused on downloading and chatting with local models | Self-hosted chat UI that talks to backends such as Ollama |
| Primary interface | ollama CLI, HTTP API on port 11434, optional app |
GUI first; local server features for apps | Browser UI; you point it at an API |
| Best when | You want a stable local OpenAI-style API for scripts, agents, and other apps | You want a polished desktop chat/download experience without wiring a server first | You want a private ChatGPT-like front end on top of an existing runner |
| Typical failure mode | GPU discovery, pull/proxy, queue 503, wrong model tag (404) | App/runtime issues inside the desktop stack (see our LM Studio tutorial) | Misconfigured backend URL, auth, or embeddings path (see our Open WebUI playbook) |
| Use together? | Yes — often the backend | Usually instead of Ollama as the runner, not under it | Yes — commonly fronts Ollama |
For desktop-first setup see LM Studio Tutorial: Run a Local LLM. For a browser UI on top of a private backend see Open WebUI Playbook: Private ChatGPT for Your Team.
Editor's note
Who this is for: developers and hobbyists running Ollama locally who hit pull stalls, CPU fallback, or HTTP errors from localhost:11434 / client SDKs.
Who this is not for: readers who only want a hosted chat product with no local binary. Ollama’s cloud tier exists (Pay as you go / Pro / Max / Team on ollama.com/pricing), but this article focuses on local runner failures.
Gotchas verified from official docs (2026-11-07):
- No log, no theory — Mac
~/.ollama/logs/server.log, Linuxjournalctl -u ollama, Windows%LOCALAPPDATA%\Ollama\server.log. - NVIDIA after suspend → reload
nvidia_uvm; keep driver ≥550 (570+ for older compute 5.0–6.2 cards). - AMD discovery timeout ~30s → upgrade to ROCm 7-compatible driver, then reboot.
- 404 on generate/chat → model name/tag missing locally; pull it or fix the spelling.
- 503 when busy → raise
OLLAMA_MAX_QUEUE/ reduce parallel load; default queue is 512. - Proxy breaks pulls → use
HTTPS_PROXYonly; avoidHTTP_PROXY. - Wrong LLM library → set
OLLAMA_LLM_LIBRARY(e.g.cpu_avx2) as a temporary bypass.
FAQ
How do I know the model is actually on the GPU?
Run ollama ps. Official FAQ output shows a Processor column: 100% GPU means fully on GPU, 100% CPU means system RAM only, and mixed percentages mean a split load. If you expected GPU and see CPU after sleep on Linux NVIDIA, reload nvidia_uvm and check the server log again.
What does a 404 from the Ollama API mean?
Per the errors docs, 404 is “Not Found” — commonly the model does not exist under that name. Confirm with ollama list, pull the tag you intend (ollama pull ...), and pass the exact name to /api/generate or /api/chat. A 502 is documented for cases such as an unreachable cloud model; that is a different failure path from a missing local tag.
Why do I get 503 even though my machine is idle?
The FAQ ties overload responses to the request queue. The server rejects additional work when the queue is full. Defaults include OLLAMA_MAX_QUEUE=512, OLLAMA_NUM_PARALLEL=1, and up to several concurrently loaded models when memory allows. Lower client concurrency, unload idle models with ollama stop, or raise the queue/parallel settings deliberately after checking VRAM with ollama ps.
Related posts on lightmind24
- AnythingLLM Not Working? Fixes for Docs, Ollama and Embeds — when the RAG UI cannot reach Ollama embeddings or docs.
- LM Studio Tutorial: Run a Local LLM — desktop alternative when you want a GUI runner instead of a server-first workflow.
- Open WebUI Playbook: Private ChatGPT for Your Team — chat UI you can point at a healthy Ollama backend.
Open the matching log file first, confirm GPU discovery with ollama ps, then fix pull/proxy or queue limits — most “Ollama not working” threads end there without reinstalling.
Last verified: 2026-11-07
Sources: Troubleshooting, FAQ, Hardware support (GPU), API errors, Cloud, docs index (llms.txt), ollama.com, Download, Pricing.
Image credit: screenshots of public docs.ollama.com troubleshooting, GPU/hardware, FAQ, and API errors pages captured for this post. Includes no AI-generated image.
댓글
댓글 쓰기