Engineering AI Hub server issues
Troubleshoot errors that occur in Engineering AI Hub due to server failures.
Server error log reference
The following table describes error log entries that can appear in the Engineering AI Hub server logs. Each error has a unique ID, log message, and detailed description to help diagnose and resolve issues.
All the errors that are listed in the following table return HTTP Response Code: 500 and are logged in the Engineering AI Hub server logs.
| Error ID | Error log | Description |
|---|---|---|
| 1000 | Internal server error. | Internal server error. This is a generic error raised when unexpected exceptions occur during router agent execution, user role information retrieval, or other critical operations. Check AI Hub Server logs for details and contact your administrator. |
| 1001 | Requested agent not found. | Requested agent not found. This error occurs when an agent is not registered in the system or when attempting to access an agent that does not exist in the router's agent registry. Verify agent registration before trying again. |
| 1003 | No licenses available. Try again later or contact your administrator. |
No licenses available. This error is raised when:
|
| 1004 | Request timed out. |
Request timed out. This error occurs when HTTP requests to agents exceed the configured timeout period, typically during agent communication (timeout limit 400 seconds) or configuration reload operations (timeout limit 30 seconds). This happens when the agent cannot process requests in time or when the LLM server is down. Causes include heavy load, network delays, or server issues. Try again or check network connectivity. |
| 1005 | Database error occurred. | Database error occurred. This is a general database error raised when database queries fail, including configuration fetch operations, license usage record retrieval, or database table listing operations. Check AI Hub Server logs for details. |
| 1006 | Database Configuration error. | Database configuration error. This error occurs when there are issues with database configuration parameters, invalid input for database operations, or when retrieving agent configurations from the database. Verify database connection settings and input parameters. |
| 1007 | Database Initialization failed. |
Database initialization failed. This error is raised when:
|
| 1008 | Database data fetch error. | Database data fetch error. This error occurs when retrieving data from the database fails, including configuration fetch operations or other data retrieval operations. Check database connectivity and AI Hub Server logs. |
| 1009 | Database insertion failed. |
Database insertion failed. This error is raised when:
|
| 1010 | Database data deletion error. |
Database data deletion error. This error occurs when:
|
| 1011 | Invalid input. |
Invalid input. This error is raised when:
|
| 1012 | Invalid JSON in configuration. | Invalid JSON in configuration. This error occurs when the configuration contains malformed JSON that cannot be parsed. Verify JSON syntax and try again. |
| 1013 | Configuration reload failed. |
Configuration reload failed. This error is raised when:
|
| 1014 | Configuration validation failed. | Configuration validation failed. This error occurs when agent configuration validation fails, either due to validation errors returned by the agent or unexpected errors during the validation process. Check configuration and AI Hub Server logs and agent logs. |
| 1015 | Configuration validation request timed out. | Configuration validation request timed out. This error is raised when the configuration validation request to an agent exceeds the timeout period. Try again or contact your administrator. |
| 1016 | Configuration delete operation failed. | Configuration delete operation failed. This error occurs when the configuration deletion operation cannot be completed due to unexpected errors or database issues. Check AI Hub Server logs and agent logs for details. |
| 1017 | Configuration fetch operation failed. | Configuration fetch operation failed. This error is raised when unable to fetch agent configuration from the database due to unexpected errors. Check AI Hub Server logs and agent logs for details. |
| 1018 | Configuration write operation failed. |
Configuration write operation failed. This error occurs when:
|
| 1019 | Unable to get agent information. |
Unable to get agent information. This error is raised when:
|
| 1020 | Unable to get router agent information. | Unable to get router agent information. This error occurs when unable to retrieve router agent configuration or metadata. Check AI Hub Server logs for details. |
| 1021 | Unable to initialize the agent. | Unable to initialize the agent. This error is raised when agent initialization fails, preventing the agent from being properly set up and ready for use. Check AI Hub Server logs and agent logs for details. |
| 1022 | Error in configuration settings json file. |
Error in configuration settings JSON file. This error occurs when:
|
| 1023 | Insufficient privilege error. |
Insufficient privilege error. This error is raised when:
|
Troubleshooting: For licensing issues, see Licensing issues. For all other errors, contact to your Administrator. To view detailed error logs, see Generating Pod Logs in Red Hat OpenShift.