Common ESA Errors

Patch Signing

From v10.0.x, all the packages, including the Protegrity developed packages, are signed by Protegrity. This ensures the integrity of the software being installed.

The following errors may occur while uploading the patch using Web UI or CLI Manager.

#The patch is signed by Protegrity signing key and the verification key is expired

Issue: This issue occurs if the verification key is expired, the following error message appears:
Error: Patch signature(s) expired. Would you like to continue installation?

Workaround:

• Click Yes to install the patch. The patch gets installed successfully.
• Click No. The patch installation gets terminated.

For more information about the Protegrity signed patch, contact Protegrity Support.

#The patch is not signed by Protegrity signing key

Issue: This issue occurs if the patch is not signed by Protegrity signing key.
Error: Signatures not found. Aborting

Workaround: Click Exit to terminate the installation process.
It is recommended to use a Protegrity signed patch.

For more information about the Protegrity signed patch, contact Protegrity Support.

Disk Space

#Insufficient disk space in the /var/log directory

Issue: This issue occurs if the disk space in the /var/log directory is insufficient.
Error: Unable to install the patch. The required disk space is insufficient for the following partition: /var/log/

Workaround: Ensure that at least 20% disk space in the /var/log directory is available to install the patch successfully.

#Insufficient disk space in the /opt/ directory

Issue: This issue occurs if the disk space in the /opt directory is insufficient.
Error: Unable to install the patch. The required disk space is insufficient for the following partition: /opt/

Workaround: Ensure that the available disk space in the /opt/tmp directory is at least twice the patch size.

#Insufficient disk space in the /OS directory

Issue: This issue occurs if the disk space in the /OS directory is insufficient.

Workaround: Ensure that at least 40% disk space in the /OS directory is available to install the patch successfully.

The space used in the OS(/) partition should not be more than 60%. If the space used is more than 60%, then you must clean up the OS(/) partition before proceeding with the patch installation process. For more information about cleaning up the OS(/) partition, refer to the documentation available at the following link.
https://my.protegrity.com/knowledge/ka04W000000nSxJQAU/

Miscellaneous

Unable to export the information while executing the cluster task using the IP address of the node.

Issue: This might occur if the task is executed using the IP address of the cluster task instead of the Hostname.

Workaround: To resolve this issue, ensure that the IP address of the cluster node is replaced with the Hostname in the task.

For more information about executing the cluster task, refer Scheduling Configuration Export to Cluster Tasks.

Basic Authentication

If you try to perform operations, such as, joining a cluster, exporting data/ configuration to a remote appliance, and so on , the operation fails with the following error:
Errorcode: 403

Issue: This issue occurs if the Basic Authentication is disabled, and you try to perform any of the following operations.

• Joining an existing cluster
• Establishing set ESA Communication
• Exporting data/configuration to a remote appliance
• Work with RADIUS authentication

Workaround: Ensure that the Can Create JWT Token permission is assigned to the role. If the Can Create JWT Token permission is not assigned to the role of the required user, then the operation fails.

To verify the Can Create JWT Token permission, from the ESA Web UI navigate to Settings > Users > Roles.

• ←Previous
• Next→