mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #5736] Rag broken in 0.3.30 - collection errors #52771
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 @arsaboo on GitHub (Sep 26, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5736
Bug Report
Installation Method
Docker
Environment
Open WebUI Version: v0.3.30
Ollama (if applicable): 0.3.12
Operating System: Ubuntu
Browser (if applicable): Chrome
Confirmation:
Rag was working until recently. But now, it stopped working:

I keep seeing these two errors in the logs:
Happy to provide any additional details.
@arsaboo commented on GitHub (Sep 26, 2024):
RAG works fine if I remove chromaDB
@mbelur commented on GitHub (Sep 26, 2024):
I see the same with milvus db as well.
@arsaboo commented on GitHub (Sep 26, 2024):
@mbelur well, that is good. At least the error is reproducible. Hopefully, someone can get to it.
@bgeneto commented on GitHub (Sep 26, 2024):
RAG works fine for me in dev branch, better yet after #5728 :-)
@arsaboo commented on GitHub (Sep 26, 2024):
@bgeneto are you using any of the external DBs?
@bgeneto commented on GitHub (Sep 26, 2024):
I prefer using Chroma DB, but tested with Chroma, Milvus, Ollama, and the built-in sentence transformer. Best results for me so far was with
jina-embeddings-v3+mxbai-rerank-xsmall-v1reranker. Ollama withmxbai-emded-large:latest+cross-encoder/ms-marco-MiniLM-L-6-v2. I can't run a stronger reranker.@tjbck commented on GitHub (Sep 26, 2024):
@mbelur milvus issue is not related to this issue #5622
@tjbck commented on GitHub (Sep 26, 2024):
In case someone comes across this in the future, this issue is most likely caused by a version mismatch between an external chromadb and internal open-webui chromadb package version, I was able to reproduce the issue with the latest chromadb image with the current main. After the version bump in the latest dev, I'm no longer able to reproduce the issue.