A client error can hide whether a server rejected a request or failed while loading a model. Ollama service logs on Linux with systemd expose startup messages, hardware detection and request errors that help locate the failure.

The system journal collects output from the ollama service. A server started separately in a terminal or container writes to that process's output instead, so its activity will not appear in the service journal.

An old error can outlive the failure that caused it. Matching a fresh request to its log entry by time, path and status distinguishes current activity from historical messages.

The macOS app stores server logs in ~/.ollama/logs/server.log. The Windows app uses %LOCALAPPDATA%\Ollama\server.log, with older server logs in server-#.log. In those folders, app.log records app activity; Windows also has upgrade.log for updates. See Ollama's log locations.

Server logs can contain prompts, local paths and credentials. Remove private values before sharing log excerpts.

Steps to view Ollama logs:

  1. Read the five most recent Ollama service log entries from the current boot.
    $ journalctl -u ollama -b -n 5 --no-pager -o cat
    time=2026-10-28T11:15:37.205+08:00 level=INFO source=runner.go:60 msg="discovering available GPUs..."
    ##### snipped #####
    [GIN] 2026/10/28 - 11:17:54 | 200 |  15.56ms |       127.0.0.1 | GET      "/api/version"

    -b limits entries to the current boot; -o cat displays messages without the journal's hostname and process prefix. System journal access requires root or journal-reading permissions, commonly through adm or systemd-journal membership. If access is denied, the journalctl commands can be prefixed with sudo. A No entries result is not proof that Ollama is healthy; the service status helps identify a missing or inactive service.

  2. Follow new Ollama service entries in the first terminal.
    $ journalctl -u ollama -b -f -n 0 -o cat

    -f waits for new entries, and -n 0 suppresses existing ones. An idle server may produce no immediate output.

  3. Send a version request to the local Ollama server from a second terminal.
    $ curl -fsS http://127.0.0.1:11434/api/version
    {"version":"0.40.12"}

    The request needs no downloaded model and leaves the server configuration unchanged.

  4. Confirm that the first terminal shows a new successful GET request for /api/version.
    [GIN] 2026/10/28 - 11:17:55 | 200 | 153.875µs |       127.0.0.1 | GET      "/api/version"

    The new timestamp, GET path and 200 status tie the entry to the request. A 4xx or 5xx status indicates a request or server error; no new entry can indicate a different server process or inaccessible logs. Ctrl+C exits journalctl without stopping Ollama.

Share this guide