Clustering Errors
The main purpose of clustering is to support High Availability. When clustered, all CipherTrust Manager appliances in the cluster (called cluster nodes or nodes) will continuously synchronize their databases with each other. The section lists errors which could possibly occur while setting up a clustered environment.
| Action | Error Information | Possible Cause | Remediation |
|---|---|---|---|
| New Cluster Created | failed to generate node certificate | There could be issues while generating CSR, signing the CSR or storing the CSR. The possible reasons of one of these happening could be as below: • Storage crunch in the system. • High CPU utilization or memory crunch due to large number of memory intensive operations. | Restart the appliance and retry. If problem persists, contact Thales Customer Support with a copy of the syslog. |
| New Cluster Created | failed to store node public address | There could be issues with the database operations. Possible reasons: • Storage crunch in the system. • Memory crunch, causing DB operation to fail. | Free up space and Restart the appliance. If problem persists, contact Thales Customer Support with a copy of the syslog. |
| Created new CSR | failed to generate new csr | High CPU utilization or memory crunch due to large number of memory intensive operations. | Restart the appliance and retry. If problem persists, contact Thales Customer Support with a copy of the syslog. |
| Created new CSR | failed to store new csr | Storage crunch in the system. | Please ensure that the disk space is available. |
| Joining node to cluster... | Unable to connect to remote cluster member | Possible reasons: • The node's network is down. • The node's firewall policy does not allow communication on 5432 port. | Please validate the network state and firewall policy of the node. |
| Joining node to cluster... | failed to install cluster server certificate | Possible reasons: • Certificate is not in PEM format. • Storage crunch | Please free up some space if there is a crunch. Create a CSR and get a signed certificate to retry. |
| Joining node to cluster... | Failed to read private key from file system | Possible reasons: • Disk I/O error due to disk corruption. • Storage crunch. | Please contact Thales Customer Support and provide them a copy of the syslog for analysis. |
| Joining node to cluster... | failed to restart cluster join service group | Possible reasons: • Storage crunch in the system. • High CPU utilization or memory crunch due to large number of memory intensive operations. | Please restart the appliance and retry. If problem persists, please contact Thales Customer Support. |
| New cluster node created | Error parsing the CSR | CSR may not be in a valid format. | Please verify that the CSR has not been altered. Please re-generate the CSR. If problem persists, please contact Thales Customer Support with a copy of the syslog. |
| New cluster node created | failed to sign the csr | Possible reasons: • NodeHost while signing the CSR does not match to the one used while generating the CSR. • System is not in sane state. | Please ensure that the parameters while generating CSR and while signing CSR are as expected. If yes, please contact Thales Customer Support with a copy of the syslog for analysis. |
| New cluster node created | failed to read cluster cert | Possible reasons: • Disk I/O error due to disk corruption. • Storage crunch. | Please restart the appliance and retry. If problem persists, please contact Thales Customer Support. |
| Node deleted | failed to delete a node with id <VALUE> | There could be issues with the database operations. Possible reasons: • Storage crunch in the system. • High CPU utilization or memory crunch due to large number of memory intensive operations. | Please restart the appliance and retry. If problem persists, please contact Thales Customer Support. |