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 #11893] Ollama shows "An Update Available" when there is no update indeed. #54409

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

Originally created by @owenzhao on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11893

Originally assigned to: @BruceMacD on GitHub.

What is the issue?

It is like https://github.com/ollama/ollama/issues/11336 , but Ollama has been already the latest.

Relevant log output

OS

macOS

GPU

Apple

CPU

Apple

Ollama version

0.11.4

Originally created by @owenzhao on GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11893 Originally assigned to: @BruceMacD on GitHub. ### What is the issue? It is like https://github.com/ollama/ollama/issues/11336 , but Ollama has been already the latest. ### Relevant log output ```shell ``` ### OS macOS ### GPU Apple ### CPU Apple ### Ollama version 0.11.4
GiteaMirror added the appbug labels 2026-04-29 05:54:14 -05:00
GiteaMirror commented 2026-04-29 05:54:16 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (Aug 13, 2025):

Hi @owenzhao, thanks for the report. Is it possible that an ollama server is running somewhere on your computer outside of the Ollama app? If so the app will connect to that, and it may be out of date.

<!-- gh-comment-id:3185963592 --> @BruceMacD commented on GitHub (Aug 13, 2025): Hi @owenzhao, thanks for the report. Is it possible that an ollama server is running somewhere on your computer outside of the Ollama app? If so the app will connect to that, and it may be out of date.
GiteaMirror commented 2026-04-29 05:54:16 -05:00
Author
Owner
Copy Link

@owenzhao commented on GitHub (Aug 14, 2025):

Hi @BruceMacD, I cannot answer your question directly as for me the answer is maybe. I just describe what I experienced.

I get Ollama by brew. I was used to getting the non-cask version. It needed to manually restart the ollama service every time after its upgrade. I uninstalled it and installed the cask version as it could restart from GUI menu.

Then someday I found the restart menu didn't work. So I filed https://github.com/ollama/ollama/issues/11336 .

After some days waiting, I decided to use manually upgrade. I used

brew install ollama --cask

Because brew upgrade didn't upgrade cask version of ollama to the latest.

Some weeks later, since the issue still existed. I decided to uninstall ollama and reinstall it. I removed everything related to ollama except ".ollama" folder as I wanted to keep my downloaded models.

But the issue still exists so I file this issue.

Currently, I used brew upgrade --greedy to upgrade ollama.

My Point

Maybe this is related to the rename of cask version of ollama. It is called ollama-app now instead of sharing the same name ollama with the non-cask version. But the renaming date was close to the date I found https://github.com/ollama/ollama/issues/11336

So my theory is, maybe the renaming causing something what you called "an ollama server is running somewhere on your computer outside of the Ollama app?" I am not sure. What do you think?

<!-- gh-comment-id:3187953435 --> @owenzhao commented on GitHub (Aug 14, 2025): Hi @BruceMacD, I cannot answer your question directly as for me the answer is maybe. I just describe what I experienced. I get Ollama by brew. I was used to getting the non-cask version. It needed to manually restart the ollama service every time after its upgrade. I uninstalled it and installed the cask version as it could restart from GUI menu. Then someday I found the restart menu didn't work. So I filed https://github.com/ollama/ollama/issues/11336 . After some days waiting, I decided to use manually upgrade. I used ```bash brew install ollama --cask ``` Because `brew upgrade` didn't upgrade cask version of ollama to the latest. Some weeks later, since the issue still existed. I decided to uninstall ollama and reinstall it. I removed everything related to ollama except ".ollama" folder as I wanted to keep my downloaded models. But the issue still exists so I file this issue. Currently, I used `brew upgrade --greedy` to upgrade ollama. ### My Point Maybe this is related to the rename of cask version of ollama. It is called ollama-app now instead of sharing the same name ollama with the non-cask version. But the renaming date was close to the date I found https://github.com/ollama/ollama/issues/11336 So my theory is, maybe the renaming causing something what you called "an ollama server is running somewhere on your computer outside of the Ollama app?" I am not sure. What do you think?
GiteaMirror commented 2026-04-29 05:54:17 -05:00
Author
Owner
Copy Link

@kostasx commented on GitHub (Aug 25, 2025):

0.11.6 seems to be solving this issue. @owenzhao can you verify?

<!-- gh-comment-id:3219825016 --> @kostasx commented on GitHub (Aug 25, 2025): 0.11.6 seems to be solving this issue. @owenzhao can you verify?
GiteaMirror commented 2026-04-29 05:54:18 -05:00
Author
Owner
Copy Link

@owenzhao commented on GitHub (Aug 25, 2025):

0.11.6 seems to be solving this issue. @owenzhao can you verify?

Just upgraded to 0.11.6 by "brew upgrade --greedy". And it still has https://github.com/ollama/ollama/issues/11336. I am not sure if this has already been solved, as 0.11.7 is released, though it has not been uploaded to brew. I will test it when it is ready.

<!-- gh-comment-id:3221853323 --> @owenzhao commented on GitHub (Aug 25, 2025): > 0.11.6 seems to be solving this issue. [@owenzhao](https://github.com/owenzhao) can you verify? Just upgraded to 0.11.6 by "brew upgrade --greedy". And it still has https://github.com/ollama/ollama/issues/11336. I am not sure if this has already been solved, as 0.11.7 is released, though it has not been uploaded to brew. I will test it when it is ready.
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 app 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#54409
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?