Elastic Compute Service:Error codes

Error code

Description

Cause and handling method

E01

Missing required parameters

One or more required parameters are missing. Specify all required parameters and retry.

E02

Conflicting parameters

The command contains mutually exclusive parameters. Specify only one. For example, in run-enclave, specify either --cpu-count or --cpu-ids, but not both.

E03

Invalid parameter type

A parameter value has an incorrect type. For example, --cpu-count in run-enclave requires an integer. Specifying a string triggers this error.

E04

Socket pair creation failure

The Enclave CLI failed to create a socket pair for enclave communication. Insufficient memory or the maximum number of open descriptors was reached. Retry the command, or restart the instance and retry.

E05

Process spawn failure

The Enclave CLI failed to spawn the enclave management process during run-enclave. Insufficient memory or the system thread limit was reached. Free system resources and retry, or restart the instance and retry.

E06

Failed to create the daemon process

Daemonizing the enclave process failed. Possible causes: insufficient memory, the system thread limit was reached, or the Enclave CLI main process is not allowed to daemonize. Free memory and retry, or restart the instance and retry.

E07

Directory read failure

The Enclave CLI failed to read the enclave socket directory (default: /var/run/ali-enclaves) during describe-enclave. Verify the directory exists and has correct permissions.

E08

Connection error

The Enclave CLI cannot connect to the enclave. Verify the enclave is started and in the RUNNING state.

E09

Socket close error

The Enclave CLI failed to close the socket, possibly because another signal interrupted the operation. Retry the command.

E10

Socket timeout configuration failure

The Enclave CLI failed to configure a timeout for the specified socket. Verify the socket is valid.

E11

Socket error

An unexpected socket error occurred.

E12

Epoll error

The Enclave CLI failed to register the enclave descriptor with epoll for event monitoring. Insufficient memory or the epoll descriptor limit was reached. Free memory and retry, or restart the instance and retry.

E13

Inotify error

The Enclave CLI failed to perform an inotify operation to monitor socket changes. Insufficient memory or the inotify watch limit was reached. Free memory and retry, or restart the instance and retry.

E14

Invalid command

The command contains invalid subcommands or parameters. Verify the subcommand and parameter names.

E15

Lock acquisition failure

The Enclave CLI failed to acquire a lock. A previous thread holding the lock encountered an exception. Retry the command, or restart the instance and retry.

E16

Thread synchronization failed

The Enclave CLI failed to join a thread after execution completed. Retry the command.

E17

Serde error

An error occurred while serializing or deserializing a command or its output. Verify the JSON data in the command is valid.

E18

File permissions error

The Enclave CLI lacks permission to modify the log file (default: /var/log/ali-enclaves/ali-enclaves.log). Verify the current user belongs to the de user group.

E19

File operation failure

The Enclave CLI failed to perform the requested file operation. Verify the target file exists and you have the required permissions.

E20

Invalid CPU configuration

The --cpu-ids parameter contains duplicate vCPU IDs. Remove duplicates so each vCPU ID appears only once.

E21

No such vCPUs available in the pool

One or more vCPU IDs in --cpu-ids are not in the available vCPU pool. Use only pool vCPUs and retry, or update /etc/ali-enclaves/allocator.yaml, restart the service, and retry.

E22

Insufficient vCPUs available in the pool

The vCPU count in run-enclave exceeds the available pool size. Reduce the count and retry, or update /etc/ali enclaves/allocator.yaml, restart the service, and retry.

E23

CPU ID error

The lscpu command returned invalid CPU online/offline information. Run lscpu and check its output for anomalies.

E24

CPU error

The lscpu command returned invalid information. Run lscpu and check its output for anomalies.

E25

Hugepage size error

The Enclave CLI used an invalid hugepage size to initialize enclave memory. Verify the Enclave CLI code has not been modified to include invalid hugepage sizes.

E26

Insufficient memory requested for the enclave image

The memory specified in run-enclave is less than the minimum required for the enclave image. Increase the memory size above the minimum requirement.

E27

Insufficient memory available

The memory specified in run-enclave exceeds the preallocated limit. Reduce the memory size and retry, or update /etc/ali-enclaves/allocator.yaml, restart the service, and retry.

E28

Invalid enclave descriptor

A descriptor error occurred when creating an enclave. View the error backtrace for details.

E29

Ioctl error

An unexpected ioctl error occurred. View the error backtrace for details.

E30

Failure to obtain image load info using ioctl

The Enclave CLI failed to obtain image load information via ioctl. View the error backtrace for details.

E31

Failure to configure memory using ioctl

The Enclave CLI failed to configure enclave memory via ioctl. View the error backtrace for details.

E32

Failure to configure vCPUs using ioctl

The Enclave CLI failed to configure enclave vCPUs via ioctl. View the error backtrace for details.

E33

Enclave startup failure using ioctl

The Enclave CLI failed to start the enclave via ioctl. View the error backtrace for details.

E34

Memory overflow

The Enclave CLI failed to load the enclave image into memory regions allocated for the enclave. For example, the region offset plus the image file size exceeds the platform's maximum address.

E35

EIF file parsing error

The Enclave CLI failed to read a section from the enclave image file into memory. Verify the enclave image file is valid.

E36

Enclave startup failure

The Enclave CLI did not receive a vsock heartbeat from the Enclave VM. The VM may have failed to start. Verify you provided a valid enclave image file.

E37

Enclave event monitoring error

An error occurred while monitoring enclave events. View the error backtrace for details.

E38

Enclave process command execution failure

The enclave process failed to execute a command sent by the Enclave CLI. Verify the enclave is running as expected.

E39

Enclave CLI cannot connect to the enclave management process

The Enclave CLI failed to connect to the enclave process, possibly because enclave creation failed due to other errors and the process stopped. Check for other Enclave CLI error codes. If none appear, view the error backtrace for details.

E40

Socket path not found

The Enclave CLI builds a socket path from the enclave ID to communicate with the enclave process. This error occurs when that socket path is not found, possibly because the enclave process is not running as expected. View the error backtrace for details.

E41

Enclave process reply failure

After the enclave process runs a command from the Enclave CLI, it sends the output back. This error occurs when the enclave process fails to send the output, possibly because the Enclave CLI is not running as expected. Retry the command.

E42

MMAP fault

The Enclave CLI failed to mmap memory for the enclave, possibly due to insufficient free memory. Free memory and retry, or restart the instance and retry.

E43

Munmap Fault

The Enclave CLI failed to munmap memory during enclave resource release. Verify the Enclave CLI code has not been modified to pass invalid parameters to munmap.

E44

Enclave console connection failure

The Enclave CLI failed to connect to the console of the specified enclave. Verify the enclave runs in Debug mode.

E45

The Enclave debug output could not be retrieved

The Enclave CLI failed to read data from the enclave console. Retry the command.

E46

Enclave console write output error

The Enclave CLI failed to display data retrieved from the enclave console. Retry the command.

E47

Integer parsing error

The enclave's vsock CID address is not a valid integer. Run enclave-cli describe-enclaves to verify the enclave CID address.

E48

Enclave image build error

The Enclave CLI failed to build the enclave image file. View the error backtrace for details.

E49

Docker image build error

The --docker-dir value in build-enclave is invalid. The Docker image cannot be built in that directory. Specify a valid directory.

E50

Docker image pull error

The Enclave CLI failed to pull the Docker image specified by --docker-uri during build-enclave. Update Docker to the community edition and retry. If the error persists, verify the --docker-uri value. See Install and use Docker and Docker Compose.

E51

Artifacts directory not found

The Enclave CLI needs a directory for intermediate files when building the enclave image. The path is derived from the ENCLAVE_CLI_ARTIFACTS or HOME environment variable. This error indicates neither variable is defined. Set at least one of them.

E52

The attachment folder was not found

The Enclave CLI failed to find the directory that stores blobs such as enclave kernel files and boot disk images. This directory is required to build the enclave image file. Retry the command.

E53

Timing fault

The Enclave CLI failed to measure the interval between consecutive debug output reads during console. Retry the command.

E54

Signal masking error

Signal masking failed after the enclave management process was created. Retry the command.

E55

Fault during signal unmasking

The Enclave CLI failed to unmask signals after spawning the enclave process. Retry the command.

E56

Logger error

An error occurred while initializing the logging system. View the error backtrace for details.