mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-24 03:02:09 -05:00
[GH-ISSUE #14340] run in K8S with multiple PODs, can not stop response #32745
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 withdb3c26ab7afor me.@EntropyYue commented on GitHub (Jun 9, 2025):
It work