This topic describes all error codes that the Enclave CLI can return.
Error code | Description | Cause and handling method |
E01 | Missing required parameters | One or more required parameters were not specified in the command. Make sure that all required parameters are specified. |
E02 | Conflicting parameters | The command includes two or more parameters that are incompatible with each other. Make sure that you specify only one of the conflicting parameters. For example, in the same |
E03 | Invalid parameter type | The value that was specified for a parameter in the command has an incorrect data type. For example, in the |
E04 | Socket pair creation failure | The Enclave CLI failed to create a socket pair, which is used to communicate with the enclave. Insufficient memory was available for the Enclave CLI, or the system reached the maximum number of open descriptors. Retry the command, or restart the instance and then retry the command. |
E05 | Process spawn failure | The Enclave CLI failed to spawn the enclave process when the Enclave CLI ran the |
E06 | Process daemonization failure | An error occurred while daemonizing the newly spawned enclave process. Insufficient memory was available to spawn the new process, the system reached the maximum number of threads, or the configuration of the Enclave CLI main process was not allowed to daemonize processes. Release specific system resources to free up memory and then retry the command. Alternatively, restart the instance and then retry the command. |
E07 | Directory read failure | The Enclave CLI failed to read data from the socket directory of the enclave, which is |
E08 | Connection error | The Enclave CLI failed to connect to the enclave. Make sure that the enclave is started and is in the |
E09 | Socket close error | The Enclave CLI failed to close the socket. The possible cause is that the socket close operation was interrupted by another signal. Retry the command. |
E10 | Socket timeout configuration failure. | The Enclave CLI failed to configure a timeout period for a specified socket. Make sure that the specified socket is valid. |
E11 | Socket error | An unexpected error occurred in the socket. |
E12 | Epoll error | The Enclave CLI failed to register the enclave descriptor with epoll for event monitoring. Insufficient memory was available to handle the requested operation, or the maximum number of descriptors that epoll can monitor was reached. Release specific system resources to free up memory and then retry the command. Alternatively, restart the instance and then retry the command. |
E13 | Inotify error | The Enclave CLI failed to perform an inotify operation to monitor the changes to a socket. Insufficient memory was available to handle the requested operation, or the maximum number of inotify watches was reached. Release specific system resources to free up memory and then retry the command. Alternatively, restart the instance and then retry the command. |
E14 | Invalid command | The command includes invalid subcommands or invalid parameters. Make sure that the subcommands and parameter names are valid. |
E15 | Lock acquisition failure | The Enclave CLI failed to obtain a lock. An exception occurred in a previous thread that holds the lock. Retry the command, or restart the instance and then retry the command. |
E16 | Thread join failure | The Enclave CLI failed to join a thread after the Enclave CLI finished executing the thread. Retry the command. |
E17 | Serde error | An error occurred while serializing or deserializing a command or command output. Make sure that the JSON data that you provide in the command is valid. |
E18 | File permissions error | You do not have the permissions to modify the log file, which is |
E19 | File operation failure | The Enclave CLI failed to perform the requested file operation. Make sure that the file on which the operation was performed exists and that you have the required permissions on the file. |
E20 | Invalid CPU configuration | Duplicate vCPU IDs were specified for the |
E21 | No such vCPUs available in the pool | One or more of the vCPU IDs that are included in the |
E22 | Insufficient vCPUs available in the pool | The number of vCPUs that was specified in the |
E23 | CPU ID error | The |
E24 | CPU error | The |
E25 | Hugepage size error | The Enclave CLI attempted to use an invalid hugepage size to initialize the enclave memory. Make sure that the Enclave CLI code has not been modified to include invalid hugepage sizes. |
E26 | Insufficient memory requested for the enclave image | The amount of memory that was specified in the |
E27 | Insufficient memory available | The amount of memory that was specified in the |
E28 | Invalid enclave descriptor | A descriptor error was returned when the Enclave CLI requested to create an enclave. View the error backtrace for more information. |
E29 | Ioctl error | An unexpected ioctl error occurred. View the error backtrace for more information. |
E30 | Failure to obtain image load info by using ioctl | The Enclave CLI failed to obtain image load information by using ioctl. View the error backtrace for more information. |
E31 | Failure to configure memory by using ioctl | The Enclave CLI failed to configure enclave memory by using ioctl. View the error backtrace for more information. |
E32 | Failure to configure vCPUs by using ioctl | The Enclave CLI failed to configure enclave vCPUs by using ioctl. View the error backtrace for more information. |
E33 | Enclave startup failure by using ioctl | The Enclave CLI failed to start the enclave by using ioctl. View the error backtrace for more information. |
E34 | Memory overflow | The Enclave CLI failed to load the enclave image file in memory regions that would be conceded to the future enclave. For example, the sum of the regions offset and the enclave image file size exceeds the maximum address of the system platform. |
E35 | EIF file parsing error | The Enclave CLI failed to read a section from the enclave image file into a memory region. Make sure that the enclave image file is valid. |
E36 | Enclave startup failure | Enclave CLI did not receive a vsock heartbeat packet after the enclave was started. The possible cause is that the enclave was corrupted and stopped before the enclave was started. Make sure that the enclave image file is invalid. |
E37 | Enclave event monitoring error | An error occurred while monitoring events from the enclave. View the error backtrace for more information. |
E38 | Enclave process command execution failure | The enclave process failed to run an enclave command that was sent by the Enclave CLI. Check whether the enclave is running as expected. |
E39 | Enclave process connection failure | The Enclave CLI failed to connect to the enclave process. The possible cause is that an enclave failed to be created due to other errors and the enclave process stopped. Check for other error codes that are returned by the Enclave CLI. If no other error codes are returned by the Enclave CLI, view the error backtrace for more information. |
E40 | Socket path not found | When the Enclave CLI manages an enclave, the Enclave CLI builds a socket path based on the enclave ID to communicate with the enclave process. This error code is returned when the socket path that corresponds to the enclave was not found. The possible cause is that the enclave process does not run as expected. View the error backtrace for more information. |
E41 | Enclave process reply failure | After the enclave process receives a command from the Enclave CLI and runs the command, the enclave process sends the command output to the Enclave CLI. This error code is returned when the enclave process failed to send a command output to the Enclave CLI. The possible cause is that the Enclave CLI does not run as expected. Retry the command. |
E42 | Enclave mmap error | The Enclave CLI failed to perform the mmap operation when the Enclave CLI allocated memory to the enclave. The possible cause is that the system has insufficient free memory. Release specific system resources to free up memory and then retry the command. Alternatively, restart the instance and then retry the command. |
E43 | Enclave munmap error | The Enclave CLI failed to perform the munmap operation when the resources of the enclave were being released. Make sure that the Enclave CLI code has not been modified to pass invalid input parameters to the munmap operation. |
E44 | Enclave console connection failure | The Enclave CLI failed to establish a connection with the console of a specified enclave. Make sure that the enclave runs in Debug mode. |
E45 | Enclave console read error | The Enclave CLI failed to read data from the console of the enclave. Retry the command. |
E46 | Enclave console write output error | The Enclave CLI failed to display the data retrieved from the console of the enclave. Retry the command. |
E47 | Integer parsing error | The vsock CID of the enclave is not a valid integer and failed to be parsed. Run the |
E48 | Enclave image build error | The Enclave CLI failed to build the enclave image file. View the error backtrace for more information. |
E49 | Docker image build error | An invalid directory was specified for the |
E50 | Docker image pull error | The Enclave CLI failed to pull the Docker image specified by the |
E51 | Artifacts directory not found | The Enclave CLI failed to identify the path to the directory that stores artifacts. The path is generated based on the |
E52 | Blobs path not found | The Enclave CLI failed to find the directory that stores blobs, such as enclave kernel files and boot disk image files. The Enclave CLI must find the directory when the Enclave CLI builds the enclave image file. Retry the command. |
E53 | Clock skew error | The Enclave CLI failed to measure the elapsed time between consecutive reads from the console of the enclave when the Enclave CLI ran the |
E54 | Signal masking error | The Enclave CLI failed to mask specific signals after the Enclave CLI spawned the enclave process. Retry the command. |
E55 | Signal unmasking error | The Enclave CLI failed to unmask specific signals after the Enclave CLI spawned the enclave process. Retry the command. |
E56 | Logger error | An error occurred while initializing the logging system. View the error backtrace for more information. |