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

[GH-ISSUE #10422] UNTIL being set to 4 minutes, --keepalive NOT being used #53361

New Issue
Closed
opened 2026-04-29 02:43:05 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-29 02:43:05 -05:00
Owner
Copy Link

Originally created by @DocHogan on GitHub (Apr 26, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10422

What is the issue?

I'm friggen stumped, and don't know what background I need to give up front here. This seems to be new behavior, I don't remember running into it previously.

If I instantiate ollama with a run command and model ("ollama run llama3.2"), then run a "ollama ps", it shows llama3.2 running, with "4 minutes" shown under an "UNTIL" heading. If I kill everything (processes included) and instantiate with "ollama run llama3.2 --keepalive -2m", the ps shows "Forever" for the until. The next time I run a model, though, the new run goes right back to a 4 minute keepalive timer.

Same behavior regardless of which model loaded.

Issue began, or I first caught it, earlier today, running ollama v0.6.4; I just updated to v0.6.6, which has same behavior.

Relevant log output

OS

Windows

GPU

Nvidia

CPU

No response

Ollama version

0.6.6

Originally created by @DocHogan on GitHub (Apr 26, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10422 ### What is the issue? I'm friggen stumped, and don't know what background I need to give up front here. This *seems* to be new behavior, I don't remember running into it previously. If I instantiate ollama with a run command and model ("ollama run llama3.2"), then run a "ollama ps", it shows llama3.2 running, with "4 minutes" shown under an "UNTIL" heading. If I kill everything (processes included) and instantiate with "ollama run llama3.2 --keepalive -2m", the ps shows "Forever" for the until. The next time I run a model, though, the new run goes right back to a 4 minute keepalive timer. Same behavior regardless of which model loaded. Issue began, or I first caught it, earlier today, running ollama v0.6.4; I just updated to v0.6.6, which has same behavior. ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU _No response_ ### Ollama version 0.6.6
GiteaMirror added the bug label 2026-04-29 02:43:05 -05:00
GiteaMirror commented 2026-04-29 02:43:10 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 26, 2025):

-2m (minus two minutes) is Forever minus two minutes or about 292 years. Try --keepalive 2m.

<!-- gh-comment-id:2832484699 --> @rick-github commented on GitHub (Apr 26, 2025): `-2m` (minus two minutes) is Forever minus two minutes or about 292 years. Try `--keepalive 2m`.
GiteaMirror commented 2026-04-29 02:43:12 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Apr 26, 2025):

Hey @DocHogan , sorry this is confusing. This is the correct behaviour though. If you don't set keepalive it will default to 5 mins (although it will show 4 mins since it rounds down). If you set it to a negative number it will stay loaded forever. I'm going to go ahead and close the issue.

<!-- gh-comment-id:2832514861 --> @pdevine commented on GitHub (Apr 26, 2025): Hey @DocHogan , sorry this is confusing. This is the correct behaviour though. If you don't set keepalive it will default to 5 mins (although it will show 4 mins since it rounds down). If you set it to a negative number it will stay loaded forever. I'm going to go ahead and close the issue.
GiteaMirror commented 2026-04-29 02:43:13 -05:00
Author
Owner
Copy Link

@DocHogan commented on GitHub (Apr 26, 2025):

Hey @DocHogan , sorry this is confusing. This is the correct behaviour though. If you don't set keepalive it will default to 5 mins (although it will show 4 mins since it rounds down). If you set it to a negative number it will stay loaded forever. I'm going to go ahead and close the issue.

Perfect, thank you. I don't know how I missed this behavior previously, and I've been tearing my system completely apart all day trying to track down whatever stupid thing I did to break it. Thanks!

<!-- gh-comment-id:2832537322 --> @DocHogan commented on GitHub (Apr 26, 2025): > Hey [@DocHogan](https://github.com/DocHogan) , sorry this is confusing. This is the correct behaviour though. If you don't set keepalive it will default to 5 mins (although it will show 4 mins since it rounds down). If you set it to a negative number it will stay loaded forever. I'm going to go ahead and close the issue. Perfect, thank you. I don't know how I missed this behavior previously, and I've been tearing my system completely apart all day trying to track down whatever stupid thing I did to break it. Thanks!
GiteaMirror commented 2026-04-29 02:43:14 -05:00
Author
Owner
Copy Link

@DocHogan commented on GitHub (Apr 26, 2025):

-2m (minus two minutes) is Forever minus two minutes or about 292 years. Try --keepalive 2m.

You miss the point of my issue; or, more accurately, you misunderstand my misunderstanding. :)

<!-- gh-comment-id:2832537996 --> @DocHogan commented on GitHub (Apr 26, 2025): > `-2m` (minus two minutes) is Forever minus two minutes or about 292 years. Try `--keepalive 2m`. You miss the point of my issue; or, more accurately, you misunderstand my misunderstanding. :)
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 bug
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#53361
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?