General Errors
This section lists the errors related to Alarms, NTP, SSH, and Syslogs etc.
| Action | Error Information | Possible Cause | Remediation |
|---|---|---|---|
| Acknowledge Alarm | Failed clearing alarm | Possible reasons: • Storage crunch in the system. • High CPU utilization or memory crunch due to large number of memory intensive operations. | Restart the appliance. If problem persists, contact Thales Customer Support. |
| Acknowledge Alarm | Failed acknowledging alarm | Same as above | Same as above |
| Trigger Alarm | Failed persisting alarm to database | Same as above | Same as above |
| • List Alarms • Acknowledge Alarm | Failed authorization | Uses does not have the required permissions to list or acknowledge the alarm. | Ensure that the user has rights/permissions to perform the operation. |
| Find Users | policies with conditions applied, but users endpoint does not support conditions | User does not have the rights/permissions on the Users Collection. | Ensure that the user has rights/permissions to perform the operation. |
| Find Groups | policies with conditions applied, but groups endpoint does not support conditions | User does not have the rights/permissions on the Groups Collection. | Same as above |
| • CreateKey • Find Users • Find Groups • Find Connections | authorization denied: verdict was deny | User does not have permissions to perform the requested operations. | Same as above |
| Get NTP Server | Failed to get NTP server from local Unix socket | High CPU utilization or memory crunch due to large number of memory intensive operations. | Restart system. If problem persists, contact Thales Customer Support. |
| Add NTP Server | Failed to post NTP server to local Unix socket | High CPU utilization or memory crunch due to large number of memory intensive operations. | Same as above |
| Add SSH Key | System is already bootstrapped | This operation is allowed only during system service bootstrap. If there is a non-default SSH public key configured on the system, you cannot add a second SSH key. | For Private Cloud Images (e.g. VMware, Hyper-V), the SSH key must be replaced before the system fully boots. This can be done via the CLI, API, or GUI. Refer to Starting Services After Deployment for more details. |
| Add SSH Key | Invalid SSH public key, key type is not valid | Key type is not supported. | Use the supported key type (ssh-rsa). |
| Download Logs | error creating download package for logs | Possible reasons: • Storage crunch in the system. • High CPU utilization or memory crunch due to large number of memory intensive operations. | Free up space and memory on the system and restart the appliance. If problem persists, contact Thales Customer Support. |
| • Create Syslog Connection • Update Syslog Connection | Invalid Transport | Invalid value passed in the transport field. | Provide correct values for transport. |
| • Create Interface CSR • Update Interface CSR | Write: error writing CSR parameters file | Possible reasons: • Storage crunch in the system. • High CPU utilization or memory crunch due to large number of memory intensive operations. | Free up space and memory on the system and restart the appliance. If problem persists, contact Thales Customer Support. |
• Read Interface CSR • Update Interface CSR | Error reading CSR parameters file | High CPU utilization or memory crunch due to large number of memory intensive operations. | Same as above |
