-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Knowledge base not referred to when using local Ollama #834
Labels
bug
Something isn't working
Comments
The same experience |
+1 |
xinference +1 |
KevinHuSh
added a commit
that referenced
this issue
May 20, 2024
### What problem does this PR solve? #834 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Halfknow
pushed a commit
to Halfknow/ragflow
that referenced
this issue
Nov 13, 2024
### What problem does this PR solve? infiniflow#834 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for the same bug?
Branch name
main
Commit ID
673a28e
Other environment information
Actual behavior
Ran 2 ollama, one for the embedding (port 11435) and the other for chat (port 11434).
My environment setup
Testing Steps:
Ollama models configured without problems
Change the system model settings
Knowledge base created
Retrieval testing without problems
Chat configuration
Chat fails to retrieve from knowledge base
Checked the ragflow-logs/api/*.log but can't find any useful hints
Expected behavior
It should refer to the knowledge base for answers similar to the retrieval testing.
Steps to reproduce
Additional information
Elastic search is still alive and healthy. There is remaining 1GB of free memory left. Both Ollamas didn't report any errors. Retried by clearing docker volumes and recreating the containers and making sure all other services are running first before starting ragflow main service.
The text was updated successfully, but these errors were encountered: