[PR #12553] [MERGED] logs: quiet down context canceled on completion and scheduler noise #13872

Closed
opened 2026-04-13 00:39:05 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/12553
Author: @dhiltgen
Created: 10/9/2025
Status: Merged
Merged: 10/9/2025
Merged by: @dhiltgen

Base: mainHead: reduce_noise


📝 Commits (2)

  • ab868b9 logs: quiet down context canceled on completion
  • 56ab896 quiet down scheduler log error on expected case

📊 Changes

2 files changed (+7 additions, -3 deletions)

View changed files

📝 llm/server.go (+4 -1)
📝 server/sched.go (+3 -2)

📄 Description

If the client closes the connection before Completion finishes, we were logging at error level implying the runner crashed which was misleading.

time=2025-10-08T22:59:20.566-07:00 level=ERROR source=server.go:1490 msg="post predict" error="Post \"http://127.0.0.1:57736/completion\": context canceled"

The scheduler also logged at error when an unload happens in parallel which isn't actually a failure case.

time=2025-10-09T08:25:14.744-07:00 level=DEBUG source=sched.go:360 msg="runner terminated and removed from list, blocking for VRAM recovery" runner.size="5.0 GiB" runner.vram="5.0 GiB" runner.parallel=1 runner.pid=38528 runner.model=C:\Users\daniel\.ollama\models\blobs\sha256-aeda25e63ebd698fab8638ffb778e68bed908b960d39d0becc650fa981609d25
...
time=2025-10-09T08:25:14.782-07:00 level=DEBUG source=sched.go:758 msg="no loaded runner to unload"
time=2025-10-09T08:25:14.782-07:00 level=ERROR source=sched.go:233 msg="runner to expire was nil!"

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/12553 **Author:** [@dhiltgen](https://github.com/dhiltgen) **Created:** 10/9/2025 **Status:** ✅ Merged **Merged:** 10/9/2025 **Merged by:** [@dhiltgen](https://github.com/dhiltgen) **Base:** `main` ← **Head:** `reduce_noise` --- ### 📝 Commits (2) - [`ab868b9`](https://github.com/ollama/ollama/commit/ab868b92ac3d134ffc9281e11eb76ba524c01f8e) logs: quiet down context canceled on completion - [`56ab896`](https://github.com/ollama/ollama/commit/56ab8960415c27e9bee1d9bd225658b27dcbbd5c) quiet down scheduler log error on expected case ### 📊 Changes **2 files changed** (+7 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `llm/server.go` (+4 -1) 📝 `server/sched.go` (+3 -2) </details> ### 📄 Description If the client closes the connection before Completion finishes, we were logging at error level implying the runner crashed which was misleading. ``` time=2025-10-08T22:59:20.566-07:00 level=ERROR source=server.go:1490 msg="post predict" error="Post \"http://127.0.0.1:57736/completion\": context canceled" ``` The scheduler also logged at error when an unload happens in parallel which isn't actually a failure case. ``` time=2025-10-09T08:25:14.744-07:00 level=DEBUG source=sched.go:360 msg="runner terminated and removed from list, blocking for VRAM recovery" runner.size="5.0 GiB" runner.vram="5.0 GiB" runner.parallel=1 runner.pid=38528 runner.model=C:\Users\daniel\.ollama\models\blobs\sha256-aeda25e63ebd698fab8638ffb778e68bed908b960d39d0becc650fa981609d25 ... time=2025-10-09T08:25:14.782-07:00 level=DEBUG source=sched.go:758 msg="no loaded runner to unload" time=2025-10-09T08:25:14.782-07:00 level=ERROR source=sched.go:233 msg="runner to expire was nil!" ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 00:39:05 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#13872