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

[GH-ISSUE #7165] Mistral-Nemo Model Stuck in "Stopping" State After Removal #4547

New Issue
Closed
opened 2026-04-12 15:29:12 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 15:29:12 -05:00
Owner
Copy Link

Originally created by @Yash-exe on GitHub (Oct 10, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7165

What is the issue?

I recently removed the latest Mistral-Nemo 7B model using ollama rm command and noticed some strange behavior:

The mistral nemo model no longer shows up when I run ollama list
Disk space usage has returned to normal, which suggests that the model has been successfully removed. Checked this via df -k
This seems correct.

However, when I run ollama ps, the model still appears with the status "stopping..." and seems to be stuck in this state. Have attached the screenshot for reference.

What would be the correct steps to resolve this?

Screenshot 2024-10-10 at 9 05 18 AM

OS

Linux

GPU

No response

CPU

No response

Ollama version

0.3.12

Originally created by @Yash-exe on GitHub (Oct 10, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7165 ### What is the issue? I recently removed the latest Mistral-Nemo 7B model using ollama rm command and noticed some strange behavior: The mistral nemo model no longer shows up when I run **ollama list** Disk space usage has returned to normal, which suggests that the model has been successfully removed. Checked this via **df -k** This seems correct. However, when I run **ollama ps**, the model still appears with the status "stopping..." and seems to be stuck in this state. Have attached the screenshot for reference. What would be the correct steps to resolve this? ![Screenshot 2024-10-10 at 9 05 18 AM](https://github.com/user-attachments/assets/b1a37da8-266a-4e43-9a48-27e65cbd542d) ### OS Linux ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.3.12
GiteaMirror added the bug label 2026-04-12 15:29:12 -05:00
GiteaMirror commented 2026-04-12 15:29:13 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Oct 10, 2024):

Restarting ollama should clear the stale information. Note that 0.1.32 is pretty old.

<!-- gh-comment-id:2405910330 --> @rick-github commented on GitHub (Oct 10, 2024): Restarting ollama should clear the stale information. Note that 0.1.32 is pretty old.
GiteaMirror commented 2026-04-12 15:29:14 -05:00
Author
Owner
Copy Link

@Yash-exe commented on GitHub (Oct 11, 2024):

The version has been updated to 0.3.12

Stopping and starting the ollama service and running another model using ollama run llama3.2 command cleared the stale information.

<!-- gh-comment-id:2406523554 --> @Yash-exe commented on GitHub (Oct 11, 2024): The version has been updated to 0.3.12 Stopping and starting the ollama service and running another model using ollama run llama3.2 command cleared the stale information.
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#4547
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?