QingTian Error Code
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|
01 |
Missing necessary argument. |
Mandatory parameters are missing. |
Check the command parameters. |
02 |
Invalid argument provided. |
Invalid parameter. |
Check the command parameters. |
03 |
File operation failure. |
File operation error. |
Check whether the target file or directory exists. |
04 |
Ioctl get sandbox capacity failure. |
Failed to get sandbox capacity using Ioctl. |
Contact Huawei Cloud technical support. |
05 |
Ioctl define sandbox failure. |
Failed to define sandbox using Ioctl. |
Contact Huawei Cloud technical support. |
06 |
Invalid parameters provided in configuration file. |
Invalid parameters exist in the configuration file. |
Check the corresponding configuration file. |
07 |
Missing necessary parameters in configuration file. |
Mandatory parameters are missing in the configuration file. |
Check the corresponding configuration file. |
08 |
Mmap memory failure. |
Mmap memory error. |
Contact Huawei Cloud technical support. |
09 |
Ioctl add memory failure. |
Failed to increase memory using Ioctl. |
Contact Huawei Cloud technical support. |
10 |
Load image failure because provided memory is too small. |
Failed to load the image. The possible cause is that the memory size is insufficient. |
Add the memory setting when launching QingTian Enclave instances. |
11 |
Ioctl add cpu failure. |
Failed to add vCPUs using loctl. |
Contact Huawei Cloud technical support. |
12 |
Lock acquire failure. |
Failed to acquire locks. |
View the qt CLI logs and check whether permissions are correctly configured for lock files. |
13 |
Socket initialization failure. |
Failed to initialize the socket. |
Contact Huawei Cloud technical support. |
14 |
Socket binding failure. |
Failed to bind the socket. |
Contact Huawei Cloud technical support. |
15 |
Socket listen failure. |
Failed to listen to the socket. |
Contact Huawei Cloud technical support. |
16 |
Socket accept failure. |
Failed to receive the socket execution. |
Contact Huawei Cloud technical support. |
17 |
Write heartbeat to the enclave failure. |
An error occurred when the heartbeat message is written to the QingTian Enclave instance. |
Contact Huawei Cloud technical support. |
18 |
Read heartbeat from the enclave failure. |
An error occurred when the heartbeat message is read from the QingTian Enclave instance. |
Contact Huawei Cloud technical support. |
19 |
Ioctl start an enclave failure. |
Failed to start the QingTian Enclave instance using Ioctl. |
Contact Huawei Cloud technical support. |
20 |
Wait heartbeat timeout. |
Waiting for the heartbeat messages timed out. |
Add the memory setting when launching QingTian Enclave instances. If the fault persists, contact Huawei Cloud technical support. |
21 |
Get json print object failure. |
Failed to obtain the JSON printing object. |
Check whether the cjson library is normal. |
22 |
Write enclave's configuration file failure. |
Failed to generate the QingTian Enclave configuration file. |
View the qt CLI logs and check whether permissions are correctly configured for the lock files. If the fault persists, contact Huawei Cloud technical support. |
23 |
Socket connection failure |
Incorrect Socket connection |
Contact Huawei Cloud technical support. |
24 |
Write cmd to the enclave server failure. |
Failed to write commands to the QingTian Enclave server. |
Contact Huawei Cloud technical support. |
25 |
Read message from the enclave server failure. |
Failed to obtain the QingTian Enclave server information. |
Contact Huawei Cloud technical support. |
26 |
Create cjson object failure. |
Failed to create the cjson object. |
Check whether the cjson library is normal. |
27 |
Create cjson array failure. |
Failed to create the cjson array. |
Check whether the cjson library is normal. |
28 |
The required enclave is not running. |
The requested QingTian Enclave instance is not running. |
Run the qt enclave query command to query the running QingTian Enclave instance. |
29 |
Invalid enclave pid. |
Invalid QingTian Enclave PID. |
Contact Huawei Cloud technical support. |
30 |
Add number into cjson object failure. |
Failed to add a number to the cjson printing object. |
Check whether the cjson library is normal. |
31 |
Add string into cjson object failure. |
Failed to add a character string to the cjson printing object. |
Check whether the cjson library is normal. |
32 |
The required enclave is not running in the debug mode. |
The requested QingTian Enclave instance is not running in debug mode. |
Run the qt enclave query command to query the running mode of the QingTian Enclave instance. |
33 |
Enclave console read failure. |
Failed to read commands on the QingTian Enclave instance console. |
Contact Huawei Cloud technical support. |
34 |
Write img header failure. |
Failed to write the image header file during image creation. |
Contact Huawei Cloud technical support. |
35 |
Write cmdline failure. |
Failed to write cmdline during image creation. |
Contact Huawei Cloud technical support. |
36 |
Write kernel failure. |
Failed to write the kernel during image creation. |
Contact Huawei Cloud technical support. |
37 |
Write initrd failure. |
Failed to write initrd during image creation. |
Contact Huawei Cloud technical support. |
38 |
Write certificate failure. |
Failed to write the certificate during image creation. |
Contact Huawei Cloud technical support. |
39 |
Get pcr failure. |
Failed to obtain the PCR value. |
Contact Huawei Cloud technical support. |
40 |
Add signature failure. |
An error occurred for image signature during image creation. |
Contact Huawei Cloud technical support. |
41 |
Check enclave image info failure while building an eif file. |
The enclave image information is abnormal during the building of the QingTian Enclave image file. |
Contact Huawei Cloud technical support. |
42 |
The required enclave is in maintenance state. |
The requested QingTian Enclave instance is in the maintenance phase. |
Contact Huawei Cloud technical support. |
43 |
The cid has already been used. |
The CID is in use. |
Specify an idle CID. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.