OptimizeElasticsearch faied

Sanjeev_kumar_N · September 4, 2020, 1:45pm

Hi Team,

Trying to configure Camunda Optimize docker container on linux OS, getting below error while running docker run command.
I have camunda image & able to access Camunda webapps (Cockpit, Tasklist, Admin).

links Refered:

========== Docker images ==========
docker images |grep camunda
registry.camunda.cloud/optimize-ee/optimize latest 946868764048 7 weeks ago 186MB
registry.camunda.cloud/cambpm-ee/camunda-bpm-platform-ee 7.10.0 4a2d2ba36042 21 months ago 157MB

========== Docker run cmd ===============
docker run -d --name optimize registry.camunda.cloud/optimize-ee/optimize:latest
719b6fbad7ed9b6c2940614e676d787b9d3d28d93d8065bd04b95ddac9ae3650

======= OR ===========

docker run -d --name optimize -p 8090:8090 -p 8091:8091
-e OPTIMIZE_CAMUNDABPM_REST_URL=http://yourCamBpm.org/engine-rest
-e OPTIMIZE_ELASTICSEARCH_HOST=yourElasticHost
-e OPTIMIZE_ELASTICSEARCH_HTTP_PORT=9200
registry.camunda.cloud/optimize-ee/optimize:latest

------ Getting below output while accessing Engine-rest URL ------------

http://yourCamBpm.org:8080/engine-rest/engine
[{“name”:“default”}]

=========== Docker logs ===========
docker logs 719b6fbad |more
12:34:22.645 [main] INFO o.c.o.s.e.OptimizeElasticsearchClientFactory - Initializing Elasticsearch rest client…
12:34:23.055 [main] ERROR o.c.o.s.e.OptimizeElasticsearchClientFactory - Failed getting number of cluster nodes.
java.net.ConnectException: Connection refused
at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:804)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:225)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212)
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1433)
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1403)
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1373)
at org.elasticsearch.client.ClusterClient.health(ClusterClient.java:118)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.getNumberOfClusterNodes(OptimizeElasticsearchClientFactory.java:68)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.waitForElasticsearch(OptimizeElasticsearchClientFactory.java:51)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.create(OptimizeElasticsearchClientFactory.java:34)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientConfiguration.optimizeElasticsearchClient(OptimizeElasticsearchClientConfigura
tion.java:29)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientConfiguration$$EnhancerBySpringCGLIB$$f912481b$$FastClassBySpringCGLIB$$d6ed20
12:34:24.570 [main] INFO o.c.o.s.e.OptimizeElasticsearchClientFactory - No elasticsearch nodes available, waiting [2250] ms to retry connecting
12:34:26.829 [main] ERROR o.c.o.s.e.OptimizeElasticsearchClientFactory - Failed getting number of cluster nodes.
java.net.ConnectException: Connection refused
at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:804)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:225)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212)
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1433)
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1403)
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1373)
at org.elasticsearch.client.ClusterClient.health(ClusterClient.java:118)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.getNumberOfClusterNodes(OptimizeElasticsearchClientFactory.java:68)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.waitForElasticsearch(OptimizeElasticsearchClientFactory.java:51)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.create(OptimizeElasticsearchClientFactory.java:34)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientConfiguration.optimizeElasticsearchClient(OptimizeElasticsearchClientConfiguration.java

Thanks
sanjeev Kumar N

JoHeinem · September 4, 2020, 1:58pm

Hey @Sanjeev_kumar_N,

Thanks for reaching out! The logs are telling you that Optimize can’t connect to Elasticsearch. From comment I also can’t see that you’ve started Elasticsearch so far. To be able to operate, Optimize needs Elasticsearch as explained in detail here. Can you please check if an Elasticsearch instance is running on your side?

Best,
Johannes

Rahul_ch · September 11, 2020, 10:30am

Hi JoHeinem ,

I am too getting same errors regarding above issue ,
Elasticsearch instance is running.

JoHeinem · September 11, 2020, 11:21am

Hey @Rahul_ch,

Can you please share a bit more details? Otherwise, it’ll be impossible for me to understand what might be wrong. For instance:

how did you start Optimize, the Camunda Runtime Platform, and Elasticsearch?
did you change the default configuration of Optimize?
where do you run the applications? (e.g. AWS, locally, etc.)

Best,
Johannes

Rahul_ch · September 11, 2020, 12:45pm

Here it is @JoHeinem

Downloaded optimize 3.1.0 from
https://docs.camunda.org/enterprise/download/#camunda-optimize
Extracted same and started with ./optimize-demo.sh
Below commands used

docker run -d --name optimize -p 8090:8090 -p 8091:8091
-e OPTIMIZE_CAMUNDABPM_REST_URL=http://10.2xx.1xx.42:8080/engine-
rest
-e OPTIMIZE_ELASTICSEARCH_HOST=10.2xx.1xx.42
-e OPTIMIZE_ELASTICSEARCH_HTTP_PORT=9200
-v /home/rahul/OptimizeLicense.txt:/optimize/environment/OptimizeLicense.txt:ro
registry.camunda.cloud/optimize-ee/optimize:3.1.0

4.Azure cloud

Sanjeev_kumar_N · September 13, 2020, 6:50am

Hi Johannes,

Thanks for the update.

We have followed below steps to configure Camunda BPM and Camunda Optimize Elastic search.
Both the images are up and running, we are able to access Camunda BPM, getting error while accessing Camunda Optimize Elastic URL. http://localhost:8090

We are running this instance in Azure cloud ENV.

We have camunda license and support, not sure how to raise the request for Camunda support, so we have raised request in camunda fourm.
It would be great help if you can help us on the below issue.

Referred Link : https://docs.camunda.org/optimize/latest/technical-guide/setup/installation/

================ Camunda BPM docker command ==========
docker pull camunda/camunda-bpm-platform:latest

docker run -d --name camunda -p 8080:8080
-e DB_DRIVER=com.mysql.jdbc.Driver
-e DB_URL=jdbc:mysql://X.X.X.X:3306/cam_db_dev?allowPublicKeyRetrieval=true
-e DB_USERNAME=camadmin
-e DB_PASSWORD=XXXXXX
-e WAIT_FOR=X.X.X.X:3306
camunda/camunda-bpm-platform:latest

root@:# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d85470d270df camunda/camunda-bpm-platform:latest “/sbin/tini – ./cam…” 10 days ago Up 10 days 8000/tcp, 9404/tcp, 0.0.0.0: 8080->8080/tcp camunda

========== Docker Optimize images ==========

docker images |grep camunda
registry.camunda.cloud/optimize-ee/optimize latest 946868764048 7 weeks ago 186MB
registry.camunda.cloud/cambpm-ee/camunda-bpm-platform-ee 7.10.0 4a2d2ba36042 21 months ago 157MB

========== Docker run cmd for optimize-ee===============
docker run -d --name optimize registry.camunda.cloud/optimize-ee/optimize:latest
719b6fbad7ed9b6c2940614e676d787b9d3d28d93d8065bd04b95ddac9ae3650

======= OR ===========
docker run -d --name optimize -p 8090:8090 -p 8091:8091
-e OPTIMIZE_CAMUNDABPM_REST_URL=http://yourCamBpm.org/engine-rest
-e OPTIMIZE_ELASTICSEARCH_HOST=yourElasticHost
-e OPTIMIZE_ELASTICSEARCH_HTTP_PORT=9200
registry.camunda.cloud/optimize-ee/optimize:latest

XXXX@utl000:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
591ddeeea91f registry.camunda.cloud/optimize-ee/optimize:3.1.0 “/sbin/tini – ./opt…” 11 seconds ago Up 10 seconds 0.0.0.0:8090-8091->8090-8091/tcp optimize
d85470d270df camunda/camunda-bpm-platform:latest “/sbin/tini – ./cam…” 10 days ago Up 10 days 8000/tcp, 9404/tcp, 0.0.0.0:8080->8080/tcp camunda

======== Error ==============
skumar@utl0:~$ sudo docker logs 591ddeee |more
06:31:35.811 [main] INFO o.c.o.s.e.OptimizeElasticsearchClientFactory - Initializing Elasticsearch rest client…
06:31:36.233 [main] ERROR o.c.o.s.e.OptimizeElasticsearchClientFactory - Failed getting number of cluster nodes.
java.net.ConnectException: Connection refused
at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:804)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:225)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212)
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1433)
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1403)
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1373)
at org.elasticsearch.client.ClusterClient.health(ClusterClient.java:118)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.getNumberOfClusterNodes(OptimizeElasticsearchClientFactory
.java:68)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.waitForElasticsearch(OptimizeElasticsearchClientFactory.ja
va:51)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientFactory.create(OptimizeElasticsearchClientFactory.java:34)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientConfiguration.optimizeElasticsearchClient(OptimizeElasticsearchCli
entConfiguration.java:29)
at org.camunda.optimize.service.es.OptimizeElasticsearchClientConfiguration$$EnhancerBySpringCGLIB$$b2d80a75.CGLIB$optimizeElast
icsearchClient$0()
at org.camunda.optimize.service.es.OptimizeElasticsearchClientConfiguration$$EnhancerBySpringCGLIB$$b2d80a75$$FastClassBySpringC
GLIB$$1c774bf8.invoke()
at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244)
at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.
java:331)

Thanks
Sanjeev Kumar N

system · January 30, 2024, 12:37pm