github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-17 13:47:08 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #2682] Windows - Serve Mode - Need to Ctrl-C or Right Click the CMD prompt from time to time to keep things moving #79276

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

Originally created by @Shawneau on GitHub (Feb 22, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2682

Originally assigned to: @dhiltgen on GitHub.

I'm running open web ui and every once and a while Ollama's cmd prompt in serve mode just stops doing anything, not a crash, it's still up, but I need to ctrl-c or right click in the window to get it moving again. Any idea why?
image

Originally created by @Shawneau on GitHub (Feb 22, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2682 Originally assigned to: @dhiltgen on GitHub. I'm running open web ui and every once and a while Ollama's cmd prompt in serve mode just stops doing anything, not a crash, it's still up, but I need to ctrl-c or right click in the window to get it moving again. Any idea why? <img width="537" alt="image" src="https://github.com/ollama/ollama/assets/51348013/9116654d-2558-420e-b8ed-a9b7d156cf55">
GiteaMirror commented 2026-05-09 04:40:30 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Feb 22, 2024):

This is likely a bug with rendering. I've noticed similar behaviour with other processes, things like ssh or tailing logs won't update the screen without some user action.

It should not affect the running of Ollama, only the output of logs into the terminal.

<!-- gh-comment-id:1960064259 --> @mxyng commented on GitHub (Feb 22, 2024): This is likely a bug with rendering. I've noticed similar behaviour with other processes, things like ssh or tailing logs won't update the screen without some user action. It should not affect the running of Ollama, only the output of logs into the terminal.
GiteaMirror commented 2026-05-09 04:40:33 -05:00
Author
Owner
Copy Link

@Shawneau commented on GitHub (Feb 22, 2024):

This is likely a bug with rendering. I've noticed similar behaviour with other processes, things like ssh or tailing logs won't update the screen without some user action.

It should not affect the running of Ollama, only the output of logs into the terminal.

Thanks for the reply, it does seem to effect the running of Ollama though.

<!-- gh-comment-id:1960160744 --> @Shawneau commented on GitHub (Feb 22, 2024): > This is likely a bug with rendering. I've noticed similar behaviour with other processes, things like ssh or tailing logs won't update the screen without some user action. > > It should not affect the running of Ollama, only the output of logs into the terminal. Thanks for the reply, it does seem to effect the running of Ollama though.
GiteaMirror commented 2026-05-09 04:40:35 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Feb 23, 2024):

I'm unable to reproduce this on Windows 11 with cmd in Windows Terminal. Can you elaborate on your environment? Namely ollama version and model. From the screenshot, it looks like you have a 3090 and A5000.

Ollama Windows app runs in the background as a service and should not be outputting logs into a terminal. How are you running it?

<!-- gh-comment-id:1960609445 --> @mxyng commented on GitHub (Feb 23, 2024): I'm unable to reproduce this on Windows 11 with cmd in Windows Terminal. Can you elaborate on your environment? Namely ollama version and model. From the screenshot, it looks like you have a 3090 and A5000. Ollama Windows app runs in the background as a service and should not be outputting logs into a terminal. How are you running it?
GiteaMirror commented 2026-05-09 04:40:38 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 12, 2024):

In addition to what @mxyng said, this could also be an errant click in the terminal window if you have it visible on your desktop that has paused the process for a copy to happen.

I don't believe there's an ollama bug here - this sounds more like ~normal foreground windows terminal behavior. If your intent is a long running persistent process, I'd suggest letting our windows tray app manage the server, or wrap it with your own approach to capture the log someplace else and not have it in an interactive terminal.

<!-- gh-comment-id:1989679163 --> @dhiltgen commented on GitHub (Mar 12, 2024): In addition to what @mxyng said, this could also be an errant click in the terminal window if you have it visible on your desktop that has paused the process for a copy to happen. I don't believe there's an ollama bug here - this sounds more like ~normal foreground windows terminal behavior. If your intent is a long running persistent process, I'd suggest letting our windows tray app manage the server, or wrap it with your own approach to capture the log someplace else and not have it in an interactive terminal.
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
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#79276
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?