github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 08:59:13 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #1290] Auto Shutdown/kill #26426

New Issue
Closed
opened 2026-04-22 02:43:19 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-22 02:43:19 -05:00
Owner
Copy Link

Originally created by @borisnachtsheim on GitHub (Nov 27, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1290

Hi guys,

i just managed to run a zephyr model with ollama on my small ubuntu server and call the model from my home computer. Everything works fine but after couple of minutes i get this auto kill:

2023/11/27 22:28:29 llama.go:435: signal: killed
2023/11/27 22:28:29 llama.go:509: llama runner stopped successfully

Then I have to manually redo ollama serve.

How can I prevent this auto shutdown?

BJ

Originally created by @borisnachtsheim on GitHub (Nov 27, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1290 Hi guys, i just managed to run a zephyr model with ollama on my small ubuntu server and call the model from my home computer. Everything works fine but after couple of minutes i get this auto kill: 2023/11/27 22:28:29 llama.go:435: signal: killed 2023/11/27 22:28:29 llama.go:509: llama runner stopped successfully Then I have to manually redo ollama serve. How can I prevent this auto shutdown? BJ
GiteaMirror added the bug label 2026-04-22 02:43:19 -05:00
GiteaMirror commented 2026-04-22 02:43:21 -05:00
Author
Owner
Copy Link

@mchiang0610 commented on GitHub (Nov 28, 2023):

@borisnachtsheim were there other logs? Wanted to track this down so we can fix it

<!-- gh-comment-id:1830826482 --> @mchiang0610 commented on GitHub (Nov 28, 2023): @borisnachtsheim were there other logs? Wanted to track this down so we can fix it
GiteaMirror commented 2026-04-22 02:43:22 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Nov 29, 2023):

This looks like normal log output when the runner is reaped after timing out (5m). There shouldn't be a need to rerun ollama serve since the API server is still available. A new generate request will start a new runner

<!-- gh-comment-id:1832755398 --> @mxyng commented on GitHub (Nov 29, 2023): This looks like normal log output when the runner is reaped after timing out (5m). There shouldn't be a need to rerun `ollama serve` since the API server is still available. A new generate request will start a new runner
GiteaMirror commented 2026-04-22 02:43:23 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Jan 20, 2024):

Closing this since there hasn't been an update in some time and the original issue looks normal

<!-- gh-comment-id:1901364790 --> @mxyng commented on GitHub (Jan 20, 2024): Closing this since there hasn't been an update in some time and the original issue looks normal
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#26426
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?