The following steps should help you troubleshoot your Jolla Mind 2.

Restarting the services and containers

If you want to restart everything, you could either shut down the Jolla Mind 2 or restart venho-ada.service and all containers without needing to turn off the Jolla Mind 2.

Note

To do this you will need root access on the Jolla Mind 2, if you don`t have it enabled follow the steps in enable Developer mode

SSH into the Jolla Mind 2 or open the Terminal on the Jolla Mind 2. Then run the following commands:


# Switch to the root user:
devel-su
# Switch to the venho-ada-env environment:
venho-ada-env
 
# Stop the venho-ada service:
systemctl stop venho-ada.service
 
# Stop all the containers:
nerdctl compose down
 
# Start the venho-ada service again which will then also start the containers:
systemctl start venho-ada.service

Now all you have to do is wait, until all containers are running again and the KEYGEN_FAIL should be gone when logging in.

Tip

You can check if all containers are running with


nerdctl ps

See logs for each container

Containers directly associated with the Venho app are usually found within the venho.ai/venho-ada/ image location, although the application might use other containers running as well. At the time of writing this, the known containers for Venho applications are:

gateway
opaque
keygen
quadstore
qdrant
redis
ipfs
llm
pytorch-transformers
mailbox-provider
storage
ollama
processor
venho-ada-frontend-httpd-1

In order to see the logs nerdctl can be used running the following command:


# Switch to root
devel-su
# Switch to venho-ada-env environment
venho-ada-env
 
# See logs for all containers:
nerdctl compose logs -f
# See logs for a specific container (e.g., processor):
nerdctl compose logs -f processor