GenAI troubleshooting
Learn how to work around some common problems you might encounter.
Common issues and solutions
If you have one of these issues, you can use the steps in the Workaround column to try to resolve it.
Area | Issue | Cause | Workaround | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Deployment |
Deployment fails because the volume already exists. |
BlueXP workload factory for GenAI needs to create a new volume during the deployment process, but a volume already exists using the name you have specified. |
Specify a unique name to use for the new volume, and try deploying again. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deployment |
The deployment fails because BlueXP workload factory for GenAI is unable to mount the volume. |
One or more of the inbound ports required for FSx for NetApp ONTAP are closed or filtered. |
Open the following inbound ports:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Maintenance |
The AI engine fails to start, and you see the error "AI engine instance error" on the Knowledge bases page. |
The AI engine instance was corrupted or doesn't exist. |
Select the Rebuild button. BlueXP workload factory for GenAI rebuilds the infrastructure and displays the rebuild progress. When complete, your knowledge bases are reconnected to the rebuilt infrastructure and the list of knowledge bases is displayed. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Maintenance |
The AI engine fails to start, and you see the error "The GenAI engine instance is stopped" on the Knowledge bases page. |
The AI engine instance is not running. |
Use the AWS Management Console or the AWS CLI to start the AI engine instance. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Maintenance |
The AI engine fails to start, and you see the error "The GenAI engine server is not responding" on the Knowledge bases page. |
The AI engine instance is not responding. |
Use the following recovery steps: Steps
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Maintenance |
The backend Docker instance used by BlueXP workload factory for GenAI failed to start. |
The volume was deleted and the EC2 instance was restarted. |
Use the following recovery steps: Steps
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Maintenance |
The backend Docker instance used by BlueXP workload factory for GenAI failed to start. |
The root volume was deleted. |
Create a volume with a name and path, and then restart the backend Docker instance from Amazon EC2. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Maintenance |
The backend Docker instance used by BlueXP workload factory for GenAI failed to start. |
The root volume was deleted. |
Create a volume with a name and path, and then restart the backend Docker instance from Amazon EC2. |