-
Notifications
You must be signed in to change notification settings - Fork 721
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
Verba - Pip Installation not working at all on Ubuntu 24.04 #317
Comments
I tried also with: git clone https://github.com/weaviate/Verba pip install -e . No luck, always the same output (and it seems also connected to the Ollama server I'm running on host side). Always in "reconnecting", but it actually pulled correctly the model I've installed on host side and no errors when starting the verba application on terminal side about Ollama. It seems it does not work at all. |
Exact same issue here, but on Ubuntu 22.04. Have tried docker and built from source deployments, as well as dockerized Ollama and local Ollama set-ups. Everything seems to work correctly (e.g., Verba sees and connects to Ollama models) but "Reconnecting" button never goes away. Below are some logs from a built from source start-up: $ verba start ℹ Couldn't connect to Groq (https://api.groq.com/openai/v1/) ✔ Connecting new Client ℹ Connecting to Weaviate Embedded {"action":"startup","default_vectorizer_module":"none","level":"info","msg":"the default vectorizer modules is set to "none", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2024-11-27T17:40:01Z"} ✔ Succesfully Connected to Weaviate INFO: [redacted]:0 - "POST /api/connect HTTP/1.0" 200 OK I imagine that the 404's on the generate_stream and import_files are to blame but cannot track down why this error is occurring. This is a completely fresh install of Ubuntu 22.04. Only other running processes of note are Ollama and nginx (which is acting as a simple authenticated reverse proxy for public connections). |
After thorough testing of further deployments using different weaviate set-ups including local, docker, custom (via a docker endpoint), and WCS configurations, nothing has changed. Signs seem to point to this being either a websocket issue in server/api.py or frontend issue in app/util.ts. |
Hey, sorry for the late reply! Thanks for the issue, I'll look into this |
@whiskeytangofoxy I think you're right, if the I'll try to recreate the errors you all mentioned. Thanks for all the details 🚀 |
Can you also let me know what exact |
Description
No way to get Verba working on even a brand new VM Ubuntu 24.04.
Installation
If you installed via pip, please specify the version:
Lastest Python version on Ubuntu 24.04
Weaviate Deployment
Configuration
I do not have, once accessing the Verba portal, any "RAG", "Add Documents", etc. tabs.
Steps to Reproduce
Run a brand new VM based on Ubuntu 24.04 and try creating a simple python venv, then run the pip install goldenverba, set up the .env with Ollama and try to open the Verba frontend on port 8000. Once selected Local Deployment, no RAG or Add Documents tabs. No settings available.
Additional context
During the startup I get the following:
✘ Document Count retrieval failed: Query call with protocol GQL
Aggregate failed with message Error in GraphQL response: [ { "locations":
[ { "column": 12, "line": 1 } ], "message":
"Cannot query field "VERBA_Embedding_gemma2_9b" on type
"AggregateObjectsObj".", "path": null } ], for the following query:
{Aggregate{VERBA_Embedding_gemma2_9b(groupBy: ["doc_uuid"]){meta{count}
groupedBy { path value } }}}.
Additional info are:
The text was updated successfully, but these errors were encountered: