github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #10136] Where is the log file and how can I configure the location of it? #6650

New Issue
Closed
opened 2026-04-12 18:20:33 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-12 18:20:33 -05:00
Owner
Copy Link

Originally created by @khteh on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10136

https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md No, it is NOT there:

root@ollama-0:/# find . -name "*.log" -print
./var/log/bootstrap.log
./var/log/dpkg.log
./var/log/alternatives.log
./var/log/apt/history.log
./var/log/apt/term.log

It seems to be logging to the console instead of file..?

Originally created by @khteh on GitHub (Apr 5, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10136 https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md No, it is NOT there: ``` root@ollama-0:/# find . -name "*.log" -print ./var/log/bootstrap.log ./var/log/dpkg.log ./var/log/alternatives.log ./var/log/apt/history.log ./var/log/apt/term.log ``` It seems to be logging to the console instead of file..?
GiteaMirror added the question label 2026-04-12 18:20:33 -05:00
GiteaMirror commented 2026-04-12 18:20:34 -05:00
Author
Owner
Copy Link

@khteh commented on GitHub (Apr 5, 2025):

I run ollama container in a local k8s using /api/version for the probes. How can I skip the probes logs?

[ollama-0 ollama] [GIN] 2025/04/05 - 03:25:11 | 200 |      41.629µs |   192.168.0.149 | GET      "/api/version"
<!-- gh-comment-id:2780176200 --> @khteh commented on GitHub (Apr 5, 2025): I run ollama container in a local k8s using `/api/version` for the probes. How can I skip the probes logs? ``` [ollama-0 ollama] [GIN] 2025/04/05 - 03:25:11 | 200 | 41.629µs | 192.168.0.149 | GET "/api/version" ```
GiteaMirror commented 2026-04-12 18:20:35 -05:00
Author
Owner
Copy Link

@ghmer commented on GitHub (Apr 5, 2025):

https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md No, it is NOT there:

from the above link:

When you run Ollama in a container, the logs go to stdout/stderr in the container

No clue if you can suppress these messages, but I don't think so. If you explained your use case or your issue, someone might help you figure out a solution/workaround.

<!-- gh-comment-id:2780544986 --> @ghmer commented on GitHub (Apr 5, 2025): > https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md No, it is NOT there: > from the above link: > When you run Ollama in a container, the logs go to stdout/stderr in the container No clue if you can suppress these messages, but I don't think so. If you explained your use case or your issue, someone might help you figure out a solution/workaround.
GiteaMirror commented 2026-04-12 18:20:35 -05:00
Author
Owner
Copy Link

@khteh commented on GitHub (Apr 5, 2025):

This is not good for EFK logging stack. Fluentd can filter out logs based on patterns. So this is a feature enhancement request.

<!-- gh-comment-id:2780546109 --> @khteh commented on GitHub (Apr 5, 2025): This is not good for EFK logging stack. Fluentd can filter out logs based on patterns. So this is a feature enhancement request.
GiteaMirror commented 2026-04-12 18:20:35 -05:00
Author
Owner
Copy Link

@khteh commented on GitHub (Apr 7, 2026):

https://github.com/ollama/ollama/issues/15387

<!-- gh-comment-id:4199037695 --> @khteh commented on GitHub (Apr 7, 2026): https://github.com/ollama/ollama/issues/15387
GiteaMirror commented 2026-04-12 18:20:36 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 7, 2026):

Image
<!-- gh-comment-id:4199061060 --> @rick-github commented on GitHub (Apr 7, 2026): <img width="562" height="105" alt="Image" src="https://github.com/user-attachments/assets/729e36e6-524d-41dc-b8e3-5c7debb2bed5" />
GiteaMirror commented 2026-04-12 18:20:36 -05:00
Author
Owner
Copy Link

@khteh commented on GitHub (Apr 7, 2026):

I suggest logging to a physical file so that we have a choice to use a sidecar, fluentd for instance, to pick it up for downstream processing of the logs. This way, the logs stay in the file system and could be rotated.

<!-- gh-comment-id:4199131309 --> @khteh commented on GitHub (Apr 7, 2026): I suggest logging to a physical file so that we have a choice to use a sidecar, fluentd for instance, to pick it up for downstream processing of the logs. This way, the logs stay in the file system and could be rotated.
GiteaMirror commented 2026-04-12 18:20:38 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 7, 2026):

In docker, ollama output is logged to a physical file managed by the container manager, and docker logs reads from that file. If your container manager doesn't do that, you could add 2>&1 | tee /var/log/ollama.log to your run script.

<!-- gh-comment-id:4199200269 --> @rick-github commented on GitHub (Apr 7, 2026): In docker, ollama output is logged to a physical file managed by the container manager, and `docker logs` reads from that file. If your container manager doesn't do that, you could add `2>&1 | tee /var/log/ollama.log` to your run script.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#6650
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?