Troubleshooting a stand-alone Elasticsearch deployment
If you encounter issues when using the stand-alone Elasticsearch instance for metrics in your IBM Connections™ deployment, refer to these troubleshooting tips or consult the IBM® Support database for recent tech notes.
Problem | Solution |
---|---|
The Metrics UI does not display and exceptions are reported in the log file, similar to the following message: CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN "CN=elasticsearch-http, OU=ICES, O=IBM, C=US" was sent from target host:port "es-metrics.mulvm.ie.ibm.com:9200". The signer may need to be added to local trust store "D:/IBM/WebSphere/elasticsearch-metrics.p12" located in SSL configuration alias "ESCloudSSLSettings" loaded from SSL configuration file "security.xml". |
Verify that the provided trust store .p12 file was updated and copied to all Connection nodes correctly, as described in Configuring the Metrics SSL settings for Elasticsearch. |
ES logs report "dangling index" warning messages, lsimilar to the following : [2018-10-05T12:33:32,647][WARN][o.e.g.DanglingIndicesState][es-data-2][[comppackk8s-haproxy-2018.11.01/sJsYY3KQStmc-lDDb5td8A]]can not be imported as a dangling index, as index with same name already exists in cluster metadata [2018-10-05T12:33:32,647][WARN][o.e.g.DanglingIndicesState][es-data-2][[comppackk8s-retrievalservice-2018.11.01/oGYwPm8FSgaD7mkpVFORMg]]can not be imported as a dangling index, as index with same name already exists in cluster metadata |
This type of warning message is caused by an incorrect upgrade or re-deploy operation, follow the upgrade and install instructions: Deploying stand-alone Elasticsearch. |