Open dawenxi-007 opened 3 months ago
Hey @dawenxi-007 , can you print the distribution side logs if you see any.
Here is what I saw:
File "/home/ubuntu/taoz/llama-stack/llama_toolchain/distribution/server.py", line 202, in endpoint
await func(request)
File "/home/ubuntu/taoz/llama-stack/llama_toolchain/agentic_system/meta_reference/agentic_system.py", line 86, in create_agentic_system
raise ValueError("Wolfram API key not defined in config")
ValueError: Wolfram API key not defined in config
INFO: 127.0.0.1:37490 - "POST /agentic_system/create HTTP/1.1" 500 Internal Server Error
Wolfram API key not defined in config
Traceback (most recent call last):
File "/home/ubuntu/taoz/llama-stack/llama_toolchain/distribution/server.py", line 202, in endpoint
await func(request)
File "/home/ubuntu/taoz/llama-stack/llama_toolchain/agentic_system/meta_reference/agentic_system.py", line 86, in create_agentic_system
raise ValueError("Wolfram API key not defined in config")
ValueError: Wolfram API key not defined in config
INFO: 127.0.0.1:58112 - "POST /agentic_system/create HTTP/1.1" 500 Internal Server Error
Wolfram API key not defined in config
Traceback (most recent call last):
File "/home/ubuntu/taoz/llama-stack/llama_toolchain/distribution/server.py", line 202, in endpoint
await func(request)
File "/home/ubuntu/taoz/llama-stack/llama_toolchain/agentic_system/meta_reference/agentic_system.py", line 86, in create_agentic_system
raise ValueError("Wolfram API key not defined in config")
ValueError: Wolfram API key not defined in config
INFO: 127.0.0.1:54880 - "POST /agentic_system/create HTTP/1.1" 500 Internal Server Error
It was asking for Wolfram API key. I didn't see this message if I run the flow from the llama agentic system git repo.
Yeah we changed some things on how distributions manage keys ( its now in the config instead of using env variables ).
Can you run llama distribution configure --name local-llama-8b
again , that should help set up the keys properly and resolve this issue.
Yes, I noticed that change. Now the ask for set up the keys is at the configuration stage. However, shouldn't the setting for the key should be optional? Like in this case, it only asks for Wolfram API key but not Brave Search API key. Also, there could be some inference scenario may not use the related tool APIs.
Like in this case, it only asks for Wolfram API key but not Brave Search API key.
I think it just fails as soon as it needs to use the Wolfram API key. See https://github.com/meta-llama/llama-stack/blob/main/llama_toolchain/agentic_system/meta_reference/agentic_system.py#L83 The next iteration of that loop (if you did provide the wolfram key but did not provide Brave Search key) will fail at the Brave Search step.
After launching the distribution server by
"llama distribution start --name local-llama-8b --port 5000 --disable-ipv6 "
, running any inference example, for example"python examples/scripts/vacation.py localhost 5000 --disable-safety"
will give the following error: