GaiaNet-AI
ubuntu 24, gaianet start can't pass step 4.
root@VM-0-3-ubuntu:~/gaianet# gaianet start [1/5] Checking the config.json file ... 👍 Done!
You already have a private key. [2/5] Starting Qdrant instance ...
👍 Done! Qdrant instance started with pid: 12099
[3/5] Starting LlamaEdge API Server ...
* Start server with the command below ...⏳
wasmedge --dir .:./dashboard --env NODE_VERSION=0.4.21 --nn-preload default:GGML:AUTO:Llama-3.2-3B-Instruct-Q5_K_M.gguf --nn-preload embedding:GGML:AUTO:nomic-embed-text-v1.5.f16.gguf rag-api-server.wasm --model-name Llama-3.2-3B-Instruct,Nomic-embed-text-v1.5 --ctx-size 16384,8192 --batch-size 128,8192 --ubatch-size 128,8192 --prompt-template llama-3-chat,embedding --rag-policy system-message --qdrant-collection-name default --qdrant-limit 1 --qdrant-score-threshold 0.5 --context-window 1 --include-usage --web-ui ./ --socket-addr 0.0.0.0:8080 --rag-prompt "You are a tour guide in Paris, France. Use information in the following context to directly answer the question from a Paris visitor.\n----------------\n"
👍 Done! LlamaEdge API Server started with pid: 12351
* Verify the LlamaEdge-RAG API Server. Please wait seconds ...⏳
*
Seems like [4/5] the 4th step doesn't appear? What can I do to fix it ? Is it because my machine only has 2G ram?
Are you able to access your http://localhost:8080/ and see if it's running on that port?
Are you able to access your http://localhost:8080/ and see if it's running on that port?
Yes, the website is running.
Are you able to access your http://localhost:8080/ and see if it's running on that port?
Yes, the website is running.
Then I think the application should be running. Try entering a prompt and wait for a response. The response may look like it's not responsive but in fact taking its time to respond. Try wait for a few minutes then check for its output.
I'm not sure why the steps are inconsistent and sometimes not showing all the completed steps in the console when starting the node 🤔 worth looking into
root@VM-0-3-ubuntu:~/gaianet# gaianet start [1/5] Checking the config.json file ... 👍 Done!
You already have a private key. [2/5] Starting Qdrant instance ...
👍 Done! Qdrant instance started with pid: 12099[3/5] Starting LlamaEdge API Server ...
* Start server with the command below ...⏳wasmedge --dir .:./dashboard --env NODE_VERSION=0.4.21 --nn-preload default:GGML:AUTO:Llama-3.2-3B-Instruct-Q5_K_M.gguf --nn-preload embedding:GGML:AUTO:nomic-embed-text-v1.5.f16.gguf rag-api-server.wasm --model-name Llama-3.2-3B-Instruct,Nomic-embed-text-v1.5 --ctx-size 16384,8192 --batch-size 128,8192 --ubatch-size 128,8192 --prompt-template llama-3-chat,embedding --rag-policy system-message --qdrant-collection-name default --qdrant-limit 1 --qdrant-score-threshold 0.5 --context-window 1 --include-usage --web-ui ./ --socket-addr 0.0.0.0:8080 --rag-prompt "You are a tour guide in Paris, France. Use information in the following context to directly answer the question from a Paris visitor.\n----------------\n"
👍 Done! LlamaEdge API Server started with pid: 12351 * Verify the LlamaEdge-RAG API Server. Please wait seconds ...⏳ *Seems like [4/5] the 4th step doesn't appear? What can I do to fix it ? Is it because my machine only has 2G ram?
What is your machine config?
Also, possible to share your log/start-llamaedge.log?
The issue could be your machine cannot run the default Llama 3.2 3B model, you can stop and update the config to use a 1B model and see if it runs.
Alternatively, you can also run gaianet stop -> gaianet init and gaianet start in the order to see if it starts.
Had the same issues on my machine but after trying again i was able to see the node url
What's causing the issue of the node url sometimes appearing and sometimes not? It's frustrating how it's not always showing the url as we would need it. @harishkotra
What's causing the issue of the node url sometimes appearing and sometimes not? It's frustrating how it's not always showing the url as we would need it. @harishkotra
Would be great if you can share the logs folder files when this happens the next time so that our engineering can look into the possible reason for this.
For now, the solution when you don't see the node url appear is to run the following in order:
gaianet stop
gaianet start
OR
gaianet stop
gaianet init
gaianet start