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 #4471] Warning: client version is different than Ollama version in Linux #64830

New Issue
Closed
opened 2026-05-03 18:55:01 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-05-03 18:55:01 -05:00
Owner
Copy Link

Originally created by @sohang3112 on GitHub (May 16, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/4471

What is the issue?

I had installed Ollama version 0.1.31 previously in Linux. Now after upgrading, ollama says its version is different than client version. How to fix this so that both are upgraded to 0.1.38?

$ curl -fsSL https://ollama.com/install.sh | sh     # command to upgrade ollama
$ ollama --version
ollama version is 0.1.31
Warning: client version is 0.1.38

OS

Linux

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @sohang3112 on GitHub (May 16, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/4471 ### What is the issue? I had installed Ollama version 0.1.31 previously in Linux. Now after upgrading, ollama says its version is different than client version. How to fix this so that both are upgraded to 0.1.38? ```console $ curl -fsSL https://ollama.com/install.sh | sh # command to upgrade ollama $ ollama --version ollama version is 0.1.31 Warning: client version is 0.1.38 ``` ### OS Linux ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-05-03 18:55:01 -05:00
GiteaMirror commented 2026-05-03 18:55:04 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (May 16, 2024):

@sohang3112 you'll need to restart the server. I don't know what version of Linux you're running, but if your system had systemd it should have restarted it for you automatically.

In the install script there is this part:

    SYSTEMCTL_RUNNING="$(systemctl is-system-running || true)"
    case $SYSTEMCTL_RUNNING in
        running|degraded)
            status "Enabling and starting ollama service..."
            $SUDO systemctl daemon-reload
            $SUDO systemctl enable ollama

            start_service() { $SUDO systemctl restart ollama; }
            trap start_service EXIT
            ;;
    esac

Regardless though, just restart the server and it will work.

<!-- gh-comment-id:2116067842 --> @pdevine commented on GitHub (May 16, 2024): @sohang3112 you'll need to restart the server. I don't know what version of Linux you're running, but if your system had systemd it should have restarted it for you automatically. In the install script there is this part: ``` SYSTEMCTL_RUNNING="$(systemctl is-system-running || true)" case $SYSTEMCTL_RUNNING in running|degraded) status "Enabling and starting ollama service..." $SUDO systemctl daemon-reload $SUDO systemctl enable ollama start_service() { $SUDO systemctl restart ollama; } trap start_service EXIT ;; esac ``` Regardless though, just restart the server and it will work.
GiteaMirror commented 2026-05-03 18:55:05 -05:00
Author
Owner
Copy Link

@Mostbesep commented on GitHub (Jan 30, 2025):

Or restart service manually:

for ubuntu, after update ollama to new version with

$ curl -fsSL https://ollama.com/install.sh | sh
$ ollama --version
ollama version is x.x.x
Warning: client version is x.y.z

must restart service to create new version client instance.

$ sudo systemctl restart ollama
$ ollama --version
ollama version is x.x.x
<!-- gh-comment-id:2623839941 --> @Mostbesep commented on GitHub (Jan 30, 2025): Or restart service manually: for ubuntu, after update ollama to new version with ```bash $ curl -fsSL https://ollama.com/install.sh | sh $ ollama --version ollama version is x.x.x Warning: client version is x.y.z ``` must restart service to create new version client instance. ```bash $ sudo systemctl restart ollama $ ollama --version ollama version is x.x.x ```
GiteaMirror commented 2026-05-03 18:55:07 -05:00
Author
Owner
Copy Link

@darkBuddha commented on GitHub (Mar 6, 2025):

❯ ollama -v
ollama version is 0.5.13
Warning: client version is 0.5.11
❯ sudo systemctl restart ollama
❯ ollama -v
ollama version is 0.5.13
Warning: client version is 0.5.11

not working for me, what is this?

<!-- gh-comment-id:2703373921 --> @darkBuddha commented on GitHub (Mar 6, 2025): ``` ❯ ollama -v ollama version is 0.5.13 Warning: client version is 0.5.11 ❯ sudo systemctl restart ollama ❯ ollama -v ollama version is 0.5.13 Warning: client version is 0.5.11 ``` not working for me, what is this?
GiteaMirror commented 2026-05-03 18:55:07 -05:00
Author
Owner
Copy Link

@sohang3112 commented on GitHub (Mar 6, 2025):

@darkBuddha Before restarting, have you tried updating ollama, maybe that would work?

curl -fsSL https://ollama.com/install.sh | sh

<!-- gh-comment-id:2703786931 --> @sohang3112 commented on GitHub (Mar 6, 2025): @darkBuddha Before restarting, have you tried updating ollama, maybe that would work? `curl -fsSL https://ollama.com/install.sh | sh`
GiteaMirror commented 2026-05-03 18:55:07 -05:00
Author
Owner
Copy Link

@darkBuddha commented on GitHub (Mar 6, 2025):

of course, also restarted systemd ollama service

<!-- gh-comment-id:2703789013 --> @darkBuddha commented on GitHub (Mar 6, 2025): of course, also restarted systemd ollama service
GiteaMirror commented 2026-05-03 18:55:08 -05:00
Author
Owner
Copy Link

@Mostbesep commented on GitHub (Mar 6, 2025):

Make sure ollama is running on systemd, not served by ollama serve command
with the command:
sudo systemctl status ollama
make sure ollama in systemd is enabled and running

<!-- gh-comment-id:2703841140 --> @Mostbesep commented on GitHub (Mar 6, 2025): Make sure ollama is running on systemd, not served by `ollama serve` command with the command: `sudo systemctl status ollama` make sure ollama in systemd is **enabled** and **running**
GiteaMirror commented 2026-05-03 18:55:08 -05:00
Author
Owner
Copy Link

@lingster commented on GitHub (May 16, 2025):

I had a similar issue, I was running the upgrade as my own account rather than root.
Fixed by removing: /usr/local/bin/ollama and reinstalling ollama.
Or I presume running the install script as root should do the trick as well...

<!-- gh-comment-id:2885915629 --> @lingster commented on GitHub (May 16, 2025): I had a similar issue, I was running the upgrade as my own account rather than root. Fixed by removing: /usr/local/bin/ollama and reinstalling ollama. Or I presume running the install script as root should do the trick as well...
GiteaMirror commented 2026-05-03 18:55:09 -05:00
Author
Owner
Copy Link

@zaimazhar commented on GitHub (Sep 7, 2025):

I faced the same problem, but in WSL2.

I installed two instances of Linux distribution; Ubuntu 22.04 and Ubuntu 24.04 (I assumed shared ext4).

I didn't realized I had v0.1.xx on Ubuntu 22.04. I uninstalled the one in Ubuntu 22.04 and ignored the latest version of Ollama in Ubuntu 24.04.

I came to check Ollama version in Ubuntu 24.04, now only it shows the latest version of Ollama without Warning: Client Version error anymore.

For uninstallation part, I referred to this markdown: https://github.com/ollama/ollama/blob/main/docs/linux.md#uninstall

<!-- gh-comment-id:3263541723 --> @zaimazhar commented on GitHub (Sep 7, 2025): I faced the same problem, but in WSL2. I installed two instances of Linux distribution; Ubuntu 22.04 and Ubuntu 24.04 (I assumed shared ext4). I didn't realized I had v0.1.xx on Ubuntu 22.04. I uninstalled the one in Ubuntu 22.04 and ignored the latest version of Ollama in Ubuntu 24.04. I came to check Ollama version in Ubuntu 24.04, now only it shows the latest version of Ollama without `Warning: Client Version` error anymore. For uninstallation part, I referred to this markdown: https://github.com/ollama/ollama/blob/main/docs/linux.md#uninstall
GiteaMirror commented 2026-05-03 18:55:09 -05:00
Author
Owner
Copy Link

@xydac commented on GitHub (Apr 23, 2026):

what helped me was
which ollama

/opt/homebrew/bin/ollama

which led me to brew upgrade ollama that fixed it for mw.

<!-- gh-comment-id:4300871328 --> @xydac commented on GitHub (Apr 23, 2026): what helped me was `which ollama` > /opt/homebrew/bin/ollama which led me to `brew upgrade ollama` that fixed it for mw.
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#64830
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?