I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Pip Install
Open WebUI Version
0.6.10
Ollama Version (if applicable)
No response
Operating System
K8S
Browser (if applicable)
No response
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have listed steps to reproduce the bug in detail.
Expected Behavior
run in K8S with multiple PODs
ask one question
wait for one moment
click stop
Error message： Task ID with XXX not fond and Output has not stopped
Actual Behavior
run in K8S with multiple PODs
ask one question
wait for one moment
click stop
Error message： Task ID with XXX not fond and Output has not stopped
Steps to Reproduce
run in K8S with multiple PODs
ask one question
wait for one moment
click stop
Error message： Task ID with XXX not fond and Output has not stopped
Logs & Screenshots
None
Additional Information
None
Originally created by @heifade on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14340
Originally assigned to: @tjbck on GitHub.
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
0.6.10
### Ollama Version (if applicable)
_No response_
### Operating System
K8S
### Browser (if applicable)
_No response_
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have listed steps to reproduce the bug in detail.
### Expected Behavior
1. run in K8S with multiple PODs
2. ask one question
3. wait for one moment
4. click stop
Error message： Task ID with XXX not fond and Output has not stopped
### Actual Behavior
1. run in K8S with multiple PODs
2. ask one question
3. wait for one moment
4. click stop
Error message： Task ID with XXX not fond and Output has not stopped
### Steps to Reproduce
1. run in K8S with multiple PODs
2. ask one question
3. wait for one moment
4. click stop
Error message： Task ID with XXX not fond and Output has not stopped
### Logs & Screenshots
None
### Additional Information
None
GiteaMirror
added the bug label 2026-05-05 18:13:03 -05:00
you run k8s with a pip installation? How? Why? Especially why?
And did you configure all the env variables necessary for parallel operations?
<!-- gh-comment-id:2909336916 -->
@Classic298 commented on GitHub (May 26, 2025):
you run k8s with a pip installation? How? Why? Especially why?
And did you configure all the env variables necessary for parallel operations?
I feel that when there are multiple PODs, the reason why the task cannot be found in the pod called by the API. Because tasks are stored in memory
When there is only one pod on K8S, this problem will not occur
@app.post("/api/tasks/stop/{task_id}")
async def stop_task_endpoint(task_id: str, user=Depends(get_verified_user)):
try:
result = await stop_task(task_id)
return result
except ValueError as e:
raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail=str(e))
<!-- gh-comment-id:2909402118 -->
@heifade commented on GitHub (May 26, 2025):
I feel that when there are multiple PODs, the reason why the task cannot be found in the pod called by the API. Because tasks are stored in memory
When there is only one pod on K8S, this problem will not occur
@app.post("/api/tasks/stop/{task_id}")
async def stop_task_endpoint(task_id: str, user=Depends(get_verified_user)):
try:
result = await stop_task(task_id)
return result
except ValueError as e:
raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail=str(e))
you run k8s with a pip installation? How? Why? Especially why?
And did you configure all the env variables necessary for parallel operations?
So you don't have that problem with a multi-replica setup? Because I can confirm this, it's an old problem that I somehow failed to report yet.
<!-- gh-comment-id:2910329615 -->
@Ithanil commented on GitHub (May 26, 2025):
> you run k8s with a pip installation? How? Why? Especially why?
>
> And did you configure all the env variables necessary for parallel operations?
So you don't have that problem with a multi-replica setup? Because I can confirm this, it's an old problem that I somehow failed to report yet.
@tjbck Although there are no errors, it still cannot be stopped; I am using docker swarm
<!-- gh-comment-id:2954889141 -->
@EntropyYue commented on GitHub (Jun 9, 2025):
@tjbck Although there are no errors, it still cannot be stopped; I am using docker swarm
Also getting the same behavior in Windows 11 > WSL2 > Docker Desktop > OpenWebUI + Ollama containers.
I also had to manually stop and start the containers and restart them.
<!-- gh-comment-id:2954899334 -->
@mikertillman commented on GitHub (Jun 9, 2025):
Also getting the same behavior in Windows 11 > WSL2 > Docker Desktop > OpenWebUI + Ollama containers.
I also had to manually stop and start the containers and restart them.
I can see the correct logs on the backend, but the messages are still being sent
<!-- gh-comment-id:2954902306 -->
@EntropyYue commented on GitHub (Jun 9, 2025):
I can see the correct logs on the backend, but the messages are still being sent
<!-- gh-comment-id:2955521090 -->
@EntropyYue commented on GitHub (Jun 9, 2025):
I can see that redis is working
<!-- gh-comment-id:2955594845 -->
@EntropyYue commented on GitHub (Jun 9, 2025):
Encountering task not found again
asyncdefstop_task(request,task_id:str):"""
Cancel a running task and remove it from the global task list.
"""ifis_redis(request):# PUBSUB: All instances check if they have this task, and stop if so.redis_send_command(request.app.state.redis,{"action":"stop","task_id":task_id,},)# Optionally check if task_id still in Redis a few moments later for feedback?return{"status":True,"message":f"Stop signal sent for {task_id}"}task=tasks.get(task_id)ifnottask:raiseValueError(f"Task with ID {task_id} not found.")task.cancel()# Request task cancellationtry:awaittask# Wait for the task to handle the cancellationexceptasyncio.CancelledError:# Task successfully canceledtasks.pop(task_id,None)# Remove it from the dictionaryreturn{"status":True,"message":f"Task {task_id} successfully stopped."}return{"status":False,"message":f"Failed to stop task {task_id}."}
is the relevant code, you'd only get 404 response if redis is not detected, are you sure you're on the lastest dev?
<!-- gh-comment-id:2955684859 -->
@tjbck commented on GitHub (Jun 9, 2025):
@EntropyYue
```py
async def stop_task(request, task_id: str):
"""
Cancel a running task and remove it from the global task list.
"""
if is_redis(request):
# PUBSUB: All instances check if they have this task, and stop if so.
redis_send_command(
request.app.state.redis,
{
"action": "stop",
"task_id": task_id,
},
)
# Optionally check if task_id still in Redis a few moments later for feedback?
return {"status": True, "message": f"Stop signal sent for {task_id}"}
task = tasks.get(task_id)
if not task:
raise ValueError(f"Task with ID {task_id} not found.")
task.cancel() # Request task cancellation
try:
await task # Wait for the task to handle the cancellation
except asyncio.CancelledError:
# Task successfully canceled
tasks.pop(task_id, None) # Remove it from the dictionary
return {"status": True, "message": f"Task {task_id} successfully stopped."}
return {"status": False, "message": f"Failed to stop task {task_id}."}
```
is the relevant code, you'd only get 404 response if redis is not detected, are you sure you're on the lastest dev?
I am sure I am on the latest dev
I have enabled debug-level logging, and here are the logs related to Redis
# docker compose logs open-webui | grep Redis
open-webui-1 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
open-webui-3 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
open-webui-4 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
open-webui-2 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
<!-- gh-comment-id:2955715850 -->
@EntropyYue commented on GitHub (Jun 9, 2025):
I am sure I am on the latest dev
I have enabled debug-level logging, and here are the logs related to Redis
```
# docker compose logs open-webui | grep Redis
open-webui-1 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
open-webui-3 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
open-webui-4 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
open-webui-2 | DEBUG [open_webui.socket.main] Using Redis to manage websockets.
```
I've merged latest dev and for me it seems to work. Using Redis Sentinel setup.
(however I once again hit an issue with usage pool cleanup preventing containers to come up properly that is present since one of the most recent version, will open an issue now)
<!-- gh-comment-id:2955737952 -->
@Ithanil commented on GitHub (Jun 9, 2025):
I've merged latest dev and for me it seems to work. Using Redis Sentinel setup.
(however I once again hit an issue with usage pool cleanup preventing containers to come up properly that is present since one of the most recent version, will open an issue now)
<!-- gh-comment-id:2955836094 -->
@Ithanil commented on GitHub (Jun 9, 2025):
Still works at at ea8dc333ee808719d3756015808986531fb9e562 , but already did with https://github.com/open-webui/open-webui/commit/db3c26ab7a3cbe30109a6397ef1ee851e7999ebb for me.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @heifade on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14340
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
0.6.10
Ollama Version (if applicable)
No response
Operating System
K8S
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Error message： Task ID with XXX not fond and Output has not stopped
Actual Behavior
Error message： Task ID with XXX not fond and Output has not stopped
Steps to Reproduce
Error message： Task ID with XXX not fond and Output has not stopped
Logs & Screenshots
None
Additional Information
None
@Classic298 commented on GitHub (May 26, 2025):
you run k8s with a pip installation? How? Why? Especially why?
And did you configure all the env variables necessary for parallel operations?
@heifade commented on GitHub (May 26, 2025):
I feel that when there are multiple PODs, the reason why the task cannot be found in the pod called by the API. Because tasks are stored in memory
When there is only one pod on K8S, this problem will not occur
@app.post("/api/tasks/stop/{task_id}")
async def stop_task_endpoint(task_id: str, user=Depends(get_verified_user)):
try:
result = await stop_task(task_id)
return result
except ValueError as e:
raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail=str(e))
@Ithanil commented on GitHub (May 26, 2025):
So you don't have that problem with a multi-replica setup? Because I can confirm this, it's an old problem that I somehow failed to report yet.
@tjbck commented on GitHub (Jun 8, 2025):
Should be addressed in dev!
@tjbck commented on GitHub (Jun 8, 2025):
@jackthgu testing wanted here
@EntropyYue commented on GitHub (Jun 9, 2025):
@tjbck Although there are no errors, it still cannot be stopped; I am using docker swarm
@mikertillman commented on GitHub (Jun 9, 2025):
Also getting the same behavior in Windows 11 > WSL2 > Docker Desktop > OpenWebUI + Ollama containers.
I also had to manually stop and start the containers and restart them.
@EntropyYue commented on GitHub (Jun 9, 2025):
I can see the correct logs on the backend, but the messages are still being sent
@tjbck commented on GitHub (Jun 9, 2025):
@EntropyYue did you configure REDIS_URL as well?
@EntropyYue commented on GitHub (Jun 9, 2025):
I configured REDIS_URL
The above is my docker compose
@EntropyYue commented on GitHub (Jun 9, 2025):
I can see that redis is working
@tjbck commented on GitHub (Jun 9, 2025):
Should be fixed with
db3c26ab7a@EntropyYue commented on GitHub (Jun 9, 2025):
Encountering task not found again
@tjbck commented on GitHub (Jun 9, 2025):
@EntropyYue is your redis configured correctly?
@EntropyYue commented on GitHub (Jun 9, 2025):
It can work, it looks like the configuration is fine
@tjbck commented on GitHub (Jun 9, 2025):
@EntropyYue
is the relevant code, you'd only get 404 response if redis is not detected, are you sure you're on the lastest dev?
@EntropyYue commented on GitHub (Jun 9, 2025):
I am sure I am on the latest dev
I have enabled debug-level logging, and here are the logs related to Redis
@Ithanil commented on GitHub (Jun 9, 2025):
I've merged latest dev and for me it seems to work. Using Redis Sentinel setup.
(however I once again hit an issue with usage pool cleanup preventing containers to come up properly that is present since one of the most recent version, will open an issue now)
@tjbck commented on GitHub (Jun 9, 2025):
@EntropyYue @Ithanil Should actually be fixed with
ea8dc333eenow, testing wanted here!@Ithanil commented on GitHub (Jun 9, 2025):
Still works at at
ea8dc333ee, but already did with https://github.com/open-webui/open-webui/commit/db3c26ab7a3cbe30109a6397ef1ee851e7999ebb for me.@EntropyYue commented on GitHub (Jun 9, 2025):
It work