Use this guide to diagnose and troubleshoot runtime issues that may occur when running MOSTLY AI. |
|
MOSTLY AI needs to be installed before using this guide. |
|
It will take 15 mins to complete this guide. |
MOSTLY AI’s components
Below you can see MOSTLY AI’s architecture diagram. It depicts how its different components interact with each other, with services in your company’s server environment, and with clients.

Application Nodes
Pod and image name | Description | Pod Lifecycle | |
---|---|---|---|
|
mostly-app |
Contains MOSTLY AI’s frontend, backend and the API. Generally reachable over port |
Always Up |
|
mostly-coordinator |
This component takes all requests from the web application and coordinates execution of tasks on the main AI engine. |
Always Up |
mostly-keycloak |
Keycloak is an open-source identity management, authentication, and authorization tool. This container has a pre-configured Keycloak instance for MOSTLY AI. |
Always Up |
|
mostly-rabbitmq |
Message queue handling communications between the AI engine and the application. |
Always Up |
|
mostly-db |
Database instance of the system. Has databases for app, coordinator and Keycloak. |
Always Up |
AI Worker nodes
Pod and image name | Description | Pod Lifecycle | |
---|---|---|---|
mostly-agent |
MOSTLY AI’s AI engine. |
Always Up |
|
mostly-engine-v2 |
The main engine component, which does the AI training and data generation. |
On Demand |
|
mostly-qa |
Engine component, which creates the Quality Assurance report for privacy and accuracy of the generated data versus the original data. |
On Demand |
|
mostly-db-connector |
Engine component responsible for the database operations. |
On Demand |
Using the command-line utilities
MOSTLY AI comes with a couple of command line utilites called mostly-ai
and mostly-agent
, that are useful for conducting basic operations on the system.
They are already in the default path, but can be located in their respective folders:
/home/<user>/<installation_folder>/mostly-ai/bin
/home/<user>/<installation_folder>/mostly-agent/bin
You can use it to start, stop, or check MOSTLY AI’s status:
Start |
|
Stop |
|
Check status |
|
and
Start |
|
Stop |
|
Check status |
|
For the full list of commands, execute mostly-ai --help
or mostly-agent --help
respectively.
Configuration file locations
The following locations contain MOSTLY AI’s configuration files and working directory. You can find them in the installation folder, which is either /home/<user>/<installation_folder>
or /opt/<installation_folder>
.
Folder | Location | Description |
---|---|---|
etc |
|
Configuration files |
data |
|
Working directory |
You can find the following configuration files in the etc
folder:
Folder | Description |
---|---|
|
Contains container definitions, their relationships and integrations. |
|
Contains |
Advanced troubleshooting
The commands below can help diagnose issues. Prefix them with sudo
if the required privileges to run them are missing.
Container health status
Command |
|
Notes |
Lists all the containers, when they were created and their status. If there is a missing container (see list of containers above), this indicates that it has stopped. |
Container logs
Command |
|
Notes |
Displays the logs of a container to the console. |