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 #6701] Windows app gets confused if wsl2 based server is still running #66254

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

Originally created by @ares0027 on GitHub (Sep 8, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6701

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

i am using ollama with open web ui but sometimes ollama refuses to launch. no error, no nothing, i double click, it does not even show up on task manager. only solution i have is restarting the pc.

checking the log file it says another instance of ollama is running, but it is not;

time=2024-09-08T13:56:31.047+03:00 level=INFO source=logging.go:50 msg="ollama app started"
time=2024-09-08T13:56:31.106+03:00 level=INFO source=lifecycle.go:70 msg="Detected another instance of ollama running, exiting"

2024-09-08 13_57_35-New Issue · ollama_ollama

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.1.19, client 0.3.8

Originally created by @ares0027 on GitHub (Sep 8, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6701 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? i am using ollama with open web ui but sometimes ollama refuses to launch. no error, no nothing, i double click, it does not even show up on task manager. only solution i have is restarting the pc. checking the log file it says another instance of ollama is running, but it is not; ``` time=2024-09-08T13:56:31.047+03:00 level=INFO source=logging.go:50 msg="ollama app started" time=2024-09-08T13:56:31.106+03:00 level=INFO source=lifecycle.go:70 msg="Detected another instance of ollama running, exiting" ``` ![2024-09-08 13_57_35-New Issue · ollama_ollama](https://github.com/user-attachments/assets/956504ca-ce06-4127-b68c-065cd09a766b) ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.1.19, client 0.3.8
GiteaMirror added the wslfeature requestwindows labels 2026-05-04 01:28:03 -05:00
GiteaMirror commented 2026-05-04 01:28:22 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Sep 8, 2024):

Your system is running a very old version of ollama as the server. Since it doesn't seem to be showing up in the task list, you can find the name and process ID of the server by opening a Powershell in administrator mode and running:

netstat -bano | Select-String -Pattern 11434 -Context 0,1

You can then check Startup Apps or Services to see where the program is launched from.

<!-- gh-comment-id:2336686833 --> @rick-github commented on GitHub (Sep 8, 2024): Your system is running a very old version of ollama as the server. Since it doesn't seem to be showing up in the task list, you can find the name and process ID of the server by opening a Powershell in administrator mode and running: ``` netstat -bano | Select-String -Pattern 11434 -Context 0,1 ``` You can then check Startup Apps or Services to see where the program is launched from.
GiteaMirror commented 2026-05-04 01:28:24 -05:00
Author
Owner
Copy Link

@ares0027 commented on GitHub (Sep 8, 2024):

Your system is running a very old version of ollama as the server. Since it doesn't seem to be showing up in the task list, you can find the name and process ID of the server by opening a Powershell in administrator mode and running:

netstat -bano | Select-String -Pattern 11434 -Context 0,1

You can then check Startup Apps or Services to see where the program is launched from.

thank you, it was wslrelay.exe. probably when i tried to use wsl to install ollama. ill try to take care of that. thank you :)

<!-- gh-comment-id:2336696455 --> @ares0027 commented on GitHub (Sep 8, 2024): > Your system is running a very old version of ollama as the server. Since it doesn't seem to be showing up in the task list, you can find the name and process ID of the server by opening a Powershell in administrator mode and running: > > ``` > netstat -bano | Select-String -Pattern 11434 -Context 0,1 > ``` > > You can then check Startup Apps or Services to see where the program is launched from. thank you, it was wslrelay.exe. probably when i tried to use wsl to install ollama. ill try to take care of that. thank you :)
GiteaMirror commented 2026-05-04 01:28:26 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Sep 9, 2024):

@ares0027 to clarify your scenario, I believe you installed ollama in WSL2, had it running as a service, and then installed the Windows app without uninstalling the WSL2 instance. This led the Windows app to see the existing server already running, so it wouldn't start the tray app. Does that sound accurate?

We should try to add some logic to detect this scenario better and report a more useful message to help guide users if possible.

<!-- gh-comment-id:2338526625 --> @dhiltgen commented on GitHub (Sep 9, 2024): @ares0027 to clarify your scenario, I believe you installed ollama in WSL2, had it running as a service, and then installed the Windows app without uninstalling the WSL2 instance. This led the Windows app to see the existing server already running, so it wouldn't start the tray app. Does that sound accurate? We should try to add some logic to detect this scenario better and report a more useful message to help guide users if possible.
GiteaMirror commented 2026-05-04 01:28:28 -05:00
Author
Owner
Copy Link

@ares0027 commented on GitHub (Sep 9, 2024):

@ares0027 to clarify your scenario, I believe you installed ollama in WSL2, had it running as a service, and then installed the Windows app without uninstalling the WSL2 instance. This led the Windows app to see the existing server already running, so it wouldn't start the tray app. Does that sound accurate?

We should try to add some logic to detect this scenario better and report a more useful message to help guide users if possible.

Yep. Exactly what i think happened. I think first i tried wsl then docker then windows app. Docker was easy to remove and i think i completely ignored/forgot wsl.

Actually a notification or something could be useful. At least in the logs just like what rick suggested it can at least tell the process name to push the user the right way. Or maybe “it is already running do you want to end this and launch this instance instead?”

<!-- gh-comment-id:2338681501 --> @ares0027 commented on GitHub (Sep 9, 2024): > @ares0027 to clarify your scenario, I believe you installed ollama in WSL2, had it running as a service, and then installed the Windows app without uninstalling the WSL2 instance. This led the Windows app to see the existing server already running, so it wouldn't start the tray app. Does that sound accurate? > > We should try to add some logic to detect this scenario better and report a more useful message to help guide users if possible. Yep. Exactly what i think happened. I think first i tried wsl then docker then windows app. Docker was easy to remove and i think i completely ignored/forgot wsl. Actually a notification or something could be useful. At least in the logs just like what rick suggested it can at least tell the process name to push the user the right way. Or maybe “it is already running do you want to end this and launch this instance instead?”
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 feature request windows wsl
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#66254
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?