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 #5334] ollama -v shows correct ollama version but different client version #49850

New Issue
Closed
opened 2026-04-28 13:11:48 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-28 13:11:48 -05:00
Owner
Copy Link

Originally created by @ganakee on GitHub (Jun 27, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5334

What is the issue?

I custom compile Ollama for AMD. I change the version file to read the custom version such as 0.1.47-amd.

Yet, when I run ollama -v within the compiled directory (I emphasize this as this is not running the ollama executable elsewhere) I see:

ollama version is 0.1.47-amd
Warning: client version is 0.1.20

The client never seems to update. (And I do not really know what client means.)

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

0.1.47

Originally created by @ganakee on GitHub (Jun 27, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5334 ### What is the issue? I custom compile Ollama for AMD. I change the version file to read the custom version such as `0.1.47-amd`. Yet, when I run `ollama -v ` within the compiled directory (I emphasize this as this is not running the ollama executable elsewhere) I see: ``` ollama version is 0.1.47-amd Warning: client version is 0.1.20 ``` The client never seems to update. (And I do not really know what client means.) ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version 0.1.47
GiteaMirror added the bug label 2026-04-28 13:11:48 -05:00
GiteaMirror commented 2026-04-28 13:11:55 -05:00
Author
Owner
Copy Link

@royjhan commented on GitHub (Jun 27, 2024):

Have you installed Ollama with a separate package manager, can you uninstall there? A similar symptom happens in MacOS with brew install ollama.

<!-- gh-comment-id:2195487041 --> @royjhan commented on GitHub (Jun 27, 2024): Have you installed Ollama with a separate package manager, can you uninstall there? A similar symptom happens in MacOS with brew install ollama.
GiteaMirror commented 2026-04-28 13:11:56 -05:00
Author
Owner
Copy Link

@Huojunning commented on GitHub (Jun 28, 2024):

ps -ef|grep ollama
kill -9 ollama

reload

<!-- gh-comment-id:2196023289 --> @Huojunning commented on GitHub (Jun 28, 2024): ps -ef|grep ollama kill -9 ollama reload
GiteaMirror commented 2026-04-28 13:11:58 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Jul 2, 2024):

@ganakee most likely you previously installed ollama with our install script, and it copied the ollama binary into your path, most likely in /usr/local/bin. You can try which ollama to see where it's finding it in your path and replace that with your custom build.

<!-- gh-comment-id:2204443094 --> @dhiltgen commented on GitHub (Jul 2, 2024): @ganakee most likely you previously installed ollama with our install script, and it copied the ollama binary into your path, most likely in /usr/local/bin. You can try `which ollama` to see where it's finding it in your path and replace that with your custom build.
GiteaMirror commented 2026-04-28 13:11:59 -05:00
Author
Owner
Copy Link

@ganakee commented on GitHub (Jul 3, 2024):

Thank you @dhiltgen and @royjhan.

Yes, this was my issue. I had originally installed on Linux via the installer script.

which ollama
/usr/local/bin/ollama

ls olla*
ollama   ollama-amd.gpu

When I custom compile, I copy the executable ollama to /usr/local/bin/ but rename it to ollama-amd.gpu (because this is a custom, AMD GPU build on ROCM). As you both noted, this resulted in ollama -v showing two versions effectively when I ran ollama -v--one showing the custom compile version and one showing the old (and forgotten) script installed ollama.

I used a symbolic link sudo ln -s ollama ollama.gpu to fix the issue. (One could also just copy the ollama executable as ollama.)

Now, when I run, I get a single entry and not the client version as reported before.:

ollama -v
ollama version is 0.1.47-AMD-ROCM61  {this is the custom name assigned during compile from my compiler directory located in` version/version.go` and will differ between users}

Thanks for the help.

Thank you to @Huojunning as well. This suggestion did not help in my case, but I understand why you suggested killing the running ollama instance and then re-running ollama--for me, from systemd as in sudo systemd restart ollamagpu.service.

<!-- gh-comment-id:2206120619 --> @ganakee commented on GitHub (Jul 3, 2024): Thank you @dhiltgen and @royjhan. Yes, this was my issue. I had originally installed on Linux via the installer script. ``` which ollama /usr/local/bin/ollama ls olla* ollama ollama-amd.gpu ``` When I custom compile, I copy the executable `ollama` to `/usr/local/bin/ `but rename it to `ollama-amd.gpu` (because this is a custom, AMD GPU build on ROCM). As you both noted, this resulted in `ollama -v `showing two versions effectively when I ran `ollama -v`--one showing the custom compile version and one showing the old (and forgotten) script installed `ollama`. I used a symbolic link `sudo ln -s ollama ollama.gpu` to fix the issue. (One could also just copy the `ollama` executable as `ollama`.) Now, when I run, I get a single entry and not the client version as reported before.: ``` ollama -v ollama version is 0.1.47-AMD-ROCM61 {this is the custom name assigned during compile from my compiler directory located in` version/version.go` and will differ between users} ``` Thanks for the help. Thank you to @Huojunning as well. This suggestion did not help in my case, but I understand why you suggested killing the running ollama instance and then re-running ollama--for me, from systemd as in `sudo systemd restart ollamagpu.service`.
GiteaMirror commented 2026-04-28 13:12:01 -05:00
Author
Owner
Copy Link

@skhatri commented on GitHub (Dec 7, 2024):

This can happen if you have an ollama already running. Kill all processes and install again to not have the mismatch.

ollama version is 0.2.7
Warning: client version is 0.5.1
<!-- gh-comment-id:2525012382 --> @skhatri commented on GitHub (Dec 7, 2024): This can happen if you have an ollama already running. Kill all processes and install again to not have the mismatch. ``` ollama version is 0.2.7 Warning: client version is 0.5.1 ```
GiteaMirror commented 2026-04-28 13:12:02 -05:00
Author
Owner
Copy Link

@stephenreid321 commented on GitHub (Jun 30, 2025):

Getting this with the latest ollama on macOS

ollama version is 0.3.4
Warning: client version is 0.9.3

<!-- gh-comment-id:3018978406 --> @stephenreid321 commented on GitHub (Jun 30, 2025): Getting this with the latest ollama on macOS ollama version is 0.3.4 Warning: client version is 0.9.3
GiteaMirror commented 2026-04-28 13:12:03 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Jun 30, 2025):

@stephenreid321 does your Ollama menu have an entry for "Restart to update" ? If so, select that to restart the server to get it running the new version.

<!-- gh-comment-id:3019648678 --> @dhiltgen commented on GitHub (Jun 30, 2025): @stephenreid321 does your Ollama menu have an entry for "Restart to update" ? If so, select that to restart the server to get it running the new version.
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#49850
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?