If you are observing an issue with the establishment of connection against the Elastic Search with the following pattern of error being observed from the logs,
YYYY-MM-DDT10:25:21.806Z [32m[jfisv][0;39m [1;31m[ERROR][0;39m [ ] [.r.ElasticsearchRestClient:103] [main] - Not able to get Elasticsearch Info YYYY-MM-DDT10:25:21.811Z [32m[jfisv][0;39m [1;31m[ERROR][0;39m [ ] [c.j.i.i.InsightService:179 ] [main] - Problem with Elastic Search : Condition returned by method "waitForElasticSearch" in class com.jfrog.insight.elasticsearch.client.rest.ElasticsearchRestClient was not fulfilled within 60 seconds. YYYY-MM-DDT10:25:21.824Z [32m[jfisv][0;39m [1;31m[ERROR][0;39m [ ] [o.s.b.SpringApplication:826 ] [main] - Application run failed java.lang.NullPointerException: nullthe possible reasons for the error could be,
- Indentation of the Elastic Search definition made in the Mission Control's system.yaml file. As a first step, verify the Elastic search configuration defined in the system.yaml file with the default template available in https://www.jfrog.com/confluence/display/JFROG/Mission+Control+System+YAML
- If the Elastic Search being used is an external one and Mission Control is not recognizing it.