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

[GH-ISSUE #1172] The server stops working after long context window is passed with zephyr model deployed with docker container on A10 GPU #596

New Issue
Closed
opened 2026-04-12 10:18:36 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 10:18:36 -05:00
Owner
Copy Link

Originally created by @ajasingh on GitHub (Nov 17, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1172

I have deployed ollama on Nvidia A10 using Docker container , it works fine or smaller context window but server starts stop to work and gives below error
2023/11/17 14:08:33 llama.go:385: signal: killed
2023/11/17 14:08:33 llama.go:459: llama runner stopped successfully

Is there any guide on why this might be happening

Originally created by @ajasingh on GitHub (Nov 17, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1172 I have deployed ollama on Nvidia A10 using Docker container , it works fine or smaller context window but server starts stop to work and gives below error 2023/11/17 14:08:33 llama.go:385: signal: killed 2023/11/17 14:08:33 llama.go:459: llama runner stopped successfully Is there any guide on why this might be happening
GiteaMirror added the bug label 2026-04-12 10:18:36 -05:00
GiteaMirror commented 2026-04-12 10:18:37 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (Nov 17, 2023):

It could be running out of memory while processing the context, are there any other logs above those ones? There should be some more specific details about why the runner is stopping in the ~20 lines above the llama runner stopped successfully log.

<!-- gh-comment-id:1816905455 --> @BruceMacD commented on GitHub (Nov 17, 2023): It could be running out of memory while processing the context, are there any other logs above those ones? There should be some more specific details about why the runner is stopping in the ~20 lines above the `llama runner stopped successfully` log.
GiteaMirror commented 2026-04-12 10:18:37 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (Mar 11, 2024):

Thanks again for bringing this issue to our attention. We've since changed how we run models so the timeout on model load will no longer occur. If anyone sees anything similar in the future please open a new issue so we can keep track of it.

<!-- gh-comment-id:1989140772 --> @BruceMacD commented on GitHub (Mar 11, 2024): Thanks again for bringing this issue to our attention. We've since changed how we run models so the timeout on model load will no longer occur. If anyone sees anything similar in the future please open a new issue so we can keep track of it.
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#596
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?