Error Types and Solutions

01: permission error

The file permission or owner group is incorrect.

Check the file permission and owner group based on the log information.

02: subprocess exception

An error occurs in the subprocess, which may be related to the shared memory size.

Check the shared memory size in the container and rectify the fault based on the error information.

03: inference service startup exception

"Server" fails to start the service.

Check the port occupation and the HTTPS service enabling status, and verify the certificate and NPU configurations based on the error information.

04: parameter parsing exception

The parsing fails due to incorrect configuration parameters.

Check the configuration file and command options based on the error information.

05: inference request generation exception

"Server" fails to convert the received data into the request body required for model inference.

Check whether the input data uses duplicate IDs or check whether the system fails to allocate memory.

06: status alarm

The status code returned when "Server" calls the interface of another component is not success, but the program running is not affected.

The program running is not affected. No action is required.

07: verification failure

The input parameter does not meet the requirements, for example, the input sequence exceeds the allowed length.

Rectify the fault based on the error information.

08: component call exception

"Server" fails to call the interface of another component.

View the logs of another component based on the error information for analysis and troubleshooting.

09: library call exception

An error is reported when the system library function is called, for example, the memory allocation fails.

Locate the fault based on the error information, check the system resource status, and check whether the OS version meets the requirements. If the compilation is performed by yourself, check your compiler version.

0A: tensor adding or obtaining exception

"Server" needs to encapsulate data into tensors that can be processed by MindIE LLM.

This error code pertains to tensor generation and is typically triggered by a system error or software bug. Contact R&D engineers for further assistance.

0B: Encode/Decode exception

An encoding or decoding exception occurs in Tokenizer.

Check whether the Tokenizer configuration path is correct and complete.

0C: response processing exception

An error is reported when a response is processed.

Responses are processed in the callback function. If an error is reported, contact R&D engineers.

0D: response generation exception

An error is reported when the model inference result is converted into an HTTP request.

Responses are processed in the callback function. If an error is reported, contact R&D engineers.

0E: JSON parsing exception

An exception occurs during JSON data parsing.

Required fields are missing in the JSON data. Rectify the fault based on the error information.

0F: timeout alarm

This alarm is generated when the inference request times out.

Check the timeout interval in the configuration file or command line options.

10: empty response alarm

The inference result received by "Server" from the model is empty.

Check MindIE LLM logs and locate the fault.

11: Pull KV alarm

Fails to obtain or pull KV cache information.

The KV cache is involved in multiple components. If an error is reported, rectify the fault based on the component logs.

12: recomputation alarm

Recomputation fails.

A recomputation error is reported in "Server".

13: security exception

The certificate check fails.

Check the HTTPS or gRPC certificate configuration and check the certificate validity based on the log information.

14: abnormal transfer

The current program cannot continue to be executed due to an exception in another module.

Locate the root cause based on the log information.

15: verification alarm

The verification fails, which does not affect program execution.

Check the alarm based on the log information.

16: unknown error

Unknown error cause.

Analyze the logs and contact R&D engineers.

17: download exception

Generally, the download fails when the URL is passed in multimodal data.

Check whether "Server" can access the input URL.

18: deletion exception

An error is reported when the cache file is deleted.

The cache file is generated when "Server" is running. The error may be caused by a software bug or an occasional OS error.

19: subprocess waiting alarm

The tokenizer in "Server" is a subprocess, which fails to be created.

The tokenizer subprocess is created during service initialization. You are advised to restart the service.

1A: subprocess exit alarm

An alarm is generated when the subprocess exits.

An alarm is generated when the IBIS subprocess or tokenizer subprocess receives an exit signal.

1B: incorrect configuration

An error occurs in the configuration file.

Check the file configuration based on the error information.

1C: initialization exception

The service of "Server" or its subcomponent fails to be initialized.

Analyze the cause of the initialization error based on the error information.

1D: service stop exception

An exception occurs when "Server" is being stopped.

Analyze the cause of the exception based on the error information.

1E: slave node exception

The slave node is abnormal.

Analyze the cause of the slave node exception based on the error information.