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 #1478] Models are sometimes lost #798

New Issue
Closed
opened 2026-04-12 10:28:36 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-12 10:28:36 -05:00
Owner
Copy Link

Originally created by @iplayfast on GitHub (Dec 12, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1478

This has happened before, and I don't know what causes it. (I'm using autogen and litellm)
ollama stalled, with my application and ended up with a timeout error.

I realized there were some defunct processes so I syscontrol stop ollama and killed every instance of ollama I could find.
Upon starting it again, it didn't have the models.

The last time it happened, I believe a reboot brought everything back.

Originally created by @iplayfast on GitHub (Dec 12, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1478 This has happened before, and I don't know what causes it. (I'm using autogen and litellm) ollama stalled, with my application and ended up with a timeout error. I realized there were some defunct processes so I syscontrol stop ollama and killed every instance of ollama I could find. Upon starting it again, it didn't have the models. The last time it happened, I believe a reboot brought everything back.
GiteaMirror added the bug label 2026-04-12 10:28:36 -05:00
GiteaMirror commented 2026-04-12 10:28:38 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (Dec 12, 2023):

This is unexpected, thanks for reporting. It looks like you are on Linux. When Ollama fails with the timeout and you restart it are you starting ollama serve or the systemctl service? Ollama runs in different contexts between those two scenarios (as the current user when using ollama server and as an ollama user when run by systemctl). So it is possible it is looking at different model directories in those cases. Next time it happens take a if you're running ollama the same way when it is restarted.

As an aside, I'll try to reproduce the timeout.

<!-- gh-comment-id:1852434121 --> @BruceMacD commented on GitHub (Dec 12, 2023): This is unexpected, thanks for reporting. It looks like you are on Linux. When Ollama fails with the timeout and you restart it are you starting `ollama serve` or the systemctl service? Ollama runs in different contexts between those two scenarios (as the current user when using `ollama server` and as an `ollama` user when run by systemctl). So it is possible it is looking at different model directories in those cases. Next time it happens take a if you're running ollama the same way when it is restarted. As an aside, I'll try to reproduce the timeout.
GiteaMirror commented 2026-04-12 10:28:38 -05:00
Author
Owner
Copy Link

@iplayfast commented on GitHub (Dec 13, 2023):

I am on linux, I believe this time I used systemctl

<!-- gh-comment-id:1853428059 --> @iplayfast commented on GitHub (Dec 13, 2023): I am on linux, I believe this time I used systemctl
GiteaMirror commented 2026-04-12 10:28:39 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Mar 12, 2024):

If you switched between ollama serve and systemctl your models will definitely be in two separate places. You can use the OLLAMA_MODELS env variable to point to the correct place and your models should show up again.

I'm going to go ahead and close the issue, but feel free to keep commenting or reopen it if you're still having problems.

<!-- gh-comment-id:1989746645 --> @pdevine commented on GitHub (Mar 12, 2024): If you switched between `ollama serve` and `systemctl` your models will definitely be in two separate places. You can use the `OLLAMA_MODELS` env variable to point to the correct place and your models should show up again. I'm going to go ahead and close the issue, but feel free to keep commenting or reopen it if you're still having problems.
GiteaMirror commented 2026-04-12 10:28:39 -05:00
Author
Owner
Copy Link

@WindSmileValley commented on GitHub (May 8, 2024):

Sometimes lost also in Win

<!-- gh-comment-id:2099592747 --> @WindSmileValley commented on GitHub (May 8, 2024): Sometimes lost also in Win
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#798
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?