#**Need help with OpenClaw + Ollama hanging on longer tasks**

1 messages · Page 1 of 1 (latest)

pale prawn
#

Environment:

  • Windows 11 (running via WSL2)
  • Ubuntu 24.04.4 LTS
  • OpenClaw: 2026.4.15 (041266a)
  • CPU: Ryzen 9 7950X
  • RAM: 64GB
  • GPU: RTX 4090 (24GB VRAM)

Current Setup:

  • Ollama + OpenWebUI working perfectly
  • All models load and run fine (good performance, memory handling looks normal)
  • OpenClaw successfully connects to Ollama
  • Can chat, switch models, and run basic tasks without issues

Problem:
When I give OpenClaw longer or more complex tasks, it eventually hangs and stops progressing.

Example behavior:

  • It starts normally
  • Runs for a while
  • Then stalls indefinitely until I manually refresh

Recent log excerpt:

Log file: /tmp/openclaw/openclaw-2026-05-02.log
17:56:25+00:00 error [tools] read failed: ENOENT: no such file or directory, access '/home/jake/.openclaw/workspace/Lees\ Site/src/index.js' raw_params={"path":"/home/jake/.openclaw/workspace/Lees\\ Site/src/index.js"}
17:57:04+00:00 error [tools] read failed: ENOENT: no such file or directory, access '/home/jake/.openclaw/workspace/Lees\ Site/src/index.js' raw_params={"path":"/home/jake/.openclaw/workspace/Lees\\ Site/src/index.js"}
18:25:39+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
18:25:39+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
gateway connect failed: GatewayClientRequestError: pairing required

Notes:

  • Reloading the page lets it start working again
  • Issue seems to happen consistently on longer-running tasks
  • I’m trying to get it to continuously work on a project without needing supervision

Models in use:

  • ollama/gemma3:27b
  • ollama/qwen3-coder:30b
  • ollama/qwen3:32b
  • ollama/gemma4

Question:
What could be causing the hanging behavior, and what should I check or change to make OpenClaw reliably run long tasks without stalling?

summer rampartBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution