Issue Station
Sign In
Tools hereToolbox

ollama - 💡(How to fix) Fix Codex fails to call tools [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15912•Fetched 2026-05-02 05:27:49
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
rnettrnett
Participants
rnettrnett
Timeline (top)
labeled ×1

Code Example

[GIN] 2026/04/30 - 20:45:35 | 404 |    182.8993ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:36 | 404 |    390.9967ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:51 | 404 |      1.5486ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:51 | 404 |     48.4534ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:56 | 200 |    5.2775931s |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:47:49 | 404 |      1.0368ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:47:49 | 404 |      1.0368ms |       127.0.0.1 | POST     "/v1/responses"
RAW_BUFFERClick to expand / collapse

What is the issue?

See https://github.com/openai/codex/issues/19871#issuecomment-4357732299

Relevant log output

Nothing bug a bunch of

[GIN] 2026/04/30 - 20:45:35 | 404 |    182.8993ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:36 | 404 |    390.9967ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:51 | 404 |      1.5486ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:51 | 404 |     48.4534ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:45:56 | 200 |    5.2775931s |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:47:49 | 404 |      1.0368ms |       127.0.0.1 | POST     "/v1/responses"
[GIN] 2026/04/30 - 20:47:49 | 404 |      1.0368ms |       127.0.0.1 | POST     "/v1/responses"

OS

Windows

GPU

No response

CPU

No response

Ollama version

0.22.0

extent analysis

TL;DR

The issue can be mitigated by investigating and resolving the root cause of the 404 errors for the "/v1/responses" endpoint.

Guidance

  • Review the routing configuration for the "/v1/responses" endpoint to ensure it is correctly defined and handled.
  • Verify that the endpoint is properly registered in the application's router.
  • Investigate potential issues with load balancing or reverse proxy configurations that may be causing the 404 errors.
  • Check for any recent changes to the application's code or configuration that may have introduced the issue.

Example

No code snippet is provided as the issue lacks specific details about the application's code.

Notes

The provided log output suggests that the issue is intermittent, with some requests returning a 200 status code while others return a 404. This may indicate a problem with the application's routing or handling of requests.

Recommendation

Apply workaround: Investigate and resolve the root cause of the 404 errors, as the issue is likely specific to the application's configuration or code.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#ssr#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

ollama - 💡(How to fix) Fix Codex fails to call tools [1 participants]