# Elastisearch deployment through boshreleases is failing

**URL:** <https://discuss.elastic.co/t/elastisearch-deployment-through-boshreleases-is-failing/226248>\
**Category:** Elasticsearch\
**Created:** [April 2, 2020, 4:05pm UTC](https://discuss.elastic.co/t/elastisearch-deployment-through-boshreleases-is-failing/226248 "2020-04-02T16:05:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nirish](https://avatars.discourse-cdn.com/v4/letter/n/8dc957/32.png) [@nirish](https://discuss.elastic.co/u/nirish)\
**Post date:** [April 2, 2020, 4:05pm UTC](https://discuss.elastic.co/t/elastisearch-deployment-through-boshreleases-is-failing/226248/1 "2020-04-02T16:05:33Z")

</div>

I am currently deploying elasticsearch(logsearch) using bosh-releases

I am using logsearch boshrelease v 208.0.0.

This deployment creates folowing instances in AWS

1. elasticsearch\_data/1
2. kibana/0
3. ingestor/0
4. elasticsearch\_data/2
5. ls-router/0
6. elasticsearch\_master/0
7. elasticsearch\_data/0
8. maintenance/0
9. cluster\_monitor/0 .

Instances successfully created were: elasticsearch\_master/0, maintenance/0, cluster\_monitor.

This current deployment is failing while creating elasticsearch\_data/0 instance.

Error message:

```auto
 Updating instance elasticsearch_data: elasticsearch_data/<instance-id>(0) (canary) (00:05:34)
                                         L Error: Action Failed get_task: Task <task-id>result: 1 of 1 post-start scripts failed. Failed Jobs: elasticsearch.
                    Task 1111 | 15:15:38 | Error: Action Failed get_task: Task <task-id> result: 1 of 1 post-start scripts failed. Failed Jobs: elasticsearch

```

I have checked both elasticsearch\_master logs(/var/vcap/sys/log/elasticsearch/elasticsearch.stdout.log) and this was only WARN message:

```
/[WARN][r.suppressed] path: /_bulk, params: {}
org.elasticsearch.transport.NodeNotConnectedException: [elasticsearch_data/0][0.0.0.0:9300] Node not connected.

```

I have checked elasticsearch\_data/0 log (/var/vcap/sys/log/elasticsearch/elasticsearch.stdout.log)  
data node was able to add elasticsearch\_master

```auto
[elasticsearch_data/0] detected_master {elasticsearch_master/0}{4IQmYSorQqC3QxjCZ5TsD
        g}{NERLgl7AQgKEAWs6HNnhAw}{10.249.1.121}{10.249.1.121:9300}, added {{elasticsearch_master/0}{4IQmYSorQqC3QxjCZ5TsDg}{NERLgl7AQgKEAWs6HNnhAw}{10.2
        49.1.121}{10.249.1.121:9300},}, reason: zen-disco-receive(from master [master {elasticsearch_master/0}{4IQmYSorQqC3QxjCZ5TsDg}{NERLgl7AQgKEAWs6HN
        nhAw}{10.249.1.121}{10.249.1.121:9300} committed version [1

```

I have checked elasticsearch\_data/0 (/var/vcap/var/vcap/sys/log/elasticsearch/post-start.stdout.log). which gives health and status of the cluster

```
body: {"cluster_name":"logsearch","status":"yellow","timed_out":false,"number_of_nodes":2,"number_of_data_nodes":1,"active_primary_shards":18,"ac
tive_shards":18,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":18,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"n
umber_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":50.0}
status:

```

In the deployment I have actually specified to disable\_post\_start: false

```
jobs:
  - consumes:
      elasticsearch:
        from: elasticsearch_master
    health:
      disable_post_start: true
      timeout: 600
    log_level: DEBUG

```

Can you give me some information or direction on why it is failing?.  
let me know if you any additional information you need.

Thanks,  
Nirish M

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 30, 2020, 4:05pm UTC](https://discuss.elastic.co/t/elastisearch-deployment-through-boshreleases-is-failing/226248/2 "2020-04-30T16:05:49Z")

</div>

Closed on April 30, 2020, 4:05pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.