6 replies

Ollama - Http 500 Error - Timeout from Client

Hey, I'm trying to run openclaw and ollama. However I'm facing some pain for particular cases (regardless of the model) when using some skill, openclaw submits a lots of info to ollama, which ollama has to "chew" for some time. I'm on a Macbook M4 with 16 RAM only... However, after 4m59s or 5m or yet 5m1s I end up with a lot of these erros:
⁨

time=2026-01-31T11:26:35.078Z level=INFO source=server.go:1385 msg="llama runner started in 4.53 seconds"
[GIN] 2026/01/31 - 11:31:31 | 500 |          5m0s |       127.0.0.1 | POST     "/v1/responses"
time=2026-01-31T11:36:30.668Z level=INFO source=runner.go:682 msg="aborting completion request due to client closing the connection"
[GIN] 2026/01/31 - 11:36:30 | 500 |         4m58s |       127.0.0.1 | POST     "/v1/responses"

time=2026-01-31T11:26:35.078Z level=INFO source=server.go:1385 msg="llama runner started in 4.53 seconds"
[GIN] 2026/01/31 - 11:31:31 | 500 |          5m0s |       127.0.0.1 | POST     "/v1/responses"
time=2026-01-31T11:36:30.668Z level=INFO source=runner.go:682 msg="aborting completion request due to client closing the connection"
[GIN] 2026/01/31 - 11:36:30 | 500 |         4m58s |       127.0.0.1 | POST     "/v1/responses"

⁩

Which innevitably ends up breaking my interaction with openclaw, since it cannot "think" and use its own inner loop, because some of the requests are interrupted before finishing... Any suggestions on how to increate timeout for inner parts of openclaw? I'd like to tweak them but all my manual changes on config haven't make a differente. Documentation barely mentions timeouts and keep-alives... not sure I have to change at node level. Any thoughts?

FotC�

Friends of the Crustacean 🦞🤝•2w ago•

6 replies

jrzabott - Daniel Junior

Ollama - Http 500 Error - Timeout from Client

time=2026-01-31T11:26:35.078Z level=INFO source=server.go:1385 msg="llama runner started in 4.53 seconds"
[GIN] 2026/01/31 - 11:31:31 | 500 |          5m0s |       127.0.0.1 | POST     "/v1/responses"
time=2026-01-31T11:36:30.668Z level=INFO source=runner.go:682 msg="aborting completion request due to client closing the connection"
[GIN] 2026/01/31 - 11:36:30 | 500 |         4m58s |       127.0.0.1 | POST     "/v1/responses"

time=2026-01-31T11:26:35.078Z level=INFO source=server.go:1385 msg="llama runner started in 4.53 seconds"
[GIN] 2026/01/31 - 11:31:31 | 500 |          5m0s |       127.0.0.1 | POST     "/v1/responses"
time=2026-01-31T11:36:30.668Z level=INFO source=runner.go:682 msg="aborting completion request due to client closing the connection"
[GIN] 2026/01/31 - 11:36:30 | 500 |         4m58s |       127.0.0.1 | POST     "/v1/responses"

Ollama - Http 500 Error - Timeout from Client

Similar Threads

Ollama - Http 500 Error - Timeout from Client

Similar Threads

Similar Threads

Similar Threads