# Ubuntu 16.04 - ansible-elasticsearch: stuck at "Wait for elasticsearch to startup"

**URL:** <https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338>\
**Category:** Elasticsearch\
**Created:** [April 23, 2017, 8:49pm UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338 "2017-04-23T20:49:15Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dextro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dextro/32/17597_2.png) [@Dextro](https://discuss.elastic.co/u/Dextro)\
**Post date:** [April 23, 2017, 8:49pm UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/1 "2017-04-23T20:49:15Z")

</div>

Ansible is stuck at "Wait for elasticsearch to startup" and just times out.  
Setup is Ubuntu 16.04.02

```
Playbook:
- name: Install and configure elasticsearch
  hosts: localhost
  remote_user: 'deploy'
  become: True
  roles:
    - role: elastic.elasticsearch

```

With just a single variable:  
`es_instance_name: "node1"`

I can't figure out what goes wrong.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 24, 2017, 1:30am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/2 "2017-04-24T01:30:12Z")

</div>

Have you looked at the ES logs?

---

<div class="post-metadata">

**Author:** ![Dextro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dextro/32/17597_2.png) [@Dextro](https://discuss.elastic.co/u/Dextro)\
**Post date:** [April 24, 2017, 7:01am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/3 "2017-04-24T07:01:01Z")

</div>

There are no logs. /var/log/elasticsearch is complete empty (no files yet).

---

<div class="post-metadata">

**Author:** ![Dextro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dextro/32/17597_2.png) [@Dextro](https://discuss.elastic.co/u/Dextro)\
**Post date:** [April 24, 2017, 7:18am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/4 "2017-04-24T07:18:06Z")

</div>

```
# systemctl enable elasticsearch
Failed to execute operation: No such file or directory

```

Something wrong with systemd.

---

<div class="post-metadata">

**Author:** ![runtman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/runtman/32/18136_2.png) [@runtman](https://discuss.elastic.co/u/runtman)\
**Post date:** [May 11, 2017, 12:50pm UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/5 "2017-05-11T12:50:32Z")

</div>

I believe it;'s the same problem as:

> [@Ansible Playbook Hangs on " Wait for elasticsearch to startup "](https://discuss.elastic.co/t/ansible-playbook-hangs-on-wait-for-elasticsearch-to-startup/78610/3):
>
> Found the issue here. The ansible role does not seem to enable the elasticsearch startp service in systemd. I added an ansible bloc to do this in the role definition.

Nothing is installed into system d, I am running into the same problem. I see no task that will take care of that either. It may be worth just adding to the playbook to do this?

---

<div class="post-metadata">

**Author:** ![mattfowler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattfowler/32/18277_2.png) [@mattfowler](https://discuss.elastic.co/u/mattfowler)\
**Post date:** [May 16, 2017, 7:33pm UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/6 "2017-05-16T19:33:58Z")

</div>

Is there a workaround for this that someone could share to enable the service in systemd? I'm having the same issue and it is blocking me currently.

---

<div class="post-metadata">

**Author:** ![runtman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/runtman/32/18136_2.png) [@runtman](https://discuss.elastic.co/u/runtman)\
**Post date:** [May 19, 2017, 9:58am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/7 "2017-05-19T09:58:58Z")

</div>

Add this to the task in /role/tasks/main.yml above "Wait for elasticsearch to startup"

```
- name: Debian - Ensure it's enabled on startup
  lineinfile:
    path: /etc/default/{{ es_instance_name }}_elasticsearch
    regexp: '^START_DAEMON='
    line: 'START_DAEMON=true'
  notify: restart elasticsearch
```

---

<div class="post-metadata">

**Author:** ![ligerdave](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@ligerdave](https://discuss.elastic.co/u/ligerdave)\
**Post date:** [May 20, 2017, 7:39am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/8 "2017-05-20T07:39:18Z")

</div>

even with adding this block, still an issue. ☹

has elastic guys tested this?

---

<div class="post-metadata">

**Author:** ![runtman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/runtman/32/18136_2.png) [@runtman](https://discuss.elastic.co/u/runtman)\
**Post date:** [May 22, 2017, 7:01am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/9 "2017-05-22T07:01:25Z")

</div>

What error are you getting?

No this code wasn't tested by Elastic.

---

<div class="post-metadata">

**Author:** ![ligerdave](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@ligerdave](https://discuss.elastic.co/u/ligerdave)\
**Post date:** [May 23, 2017, 2:45am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/10 "2017-05-23T02:45:41Z")

</div>

Fixed it. basically it didn't know which init script to execute. systemd or init.d

---

<div class="post-metadata">

**Author:** ![Ionel-Mihai\_Motoc](https://avatars.discourse-cdn.com/v4/letter/i/a4c791/32.png) [@Ionel-Mihai\_Motoc](https://discuss.elastic.co/u/Ionel-Mihai_Motoc)\
**Post date:** [May 25, 2017, 8:13am UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/11 "2017-05-25T08:13:01Z")

</div>

Hi  
Could you post here the fix you made?  
I have the same probl.

Tnx.

---

<div class="post-metadata">

**Author:** ![uschtwill](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uschtwill/32/14077_2.png) [@uschtwill](https://discuss.elastic.co/u/uschtwill)\
**Post date:** [June 13, 2017, 2:54pm UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/12 "2017-06-13T14:54:07Z")

</div>

I agree, it would be neat to have this fixed.

---

<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:** [July 11, 2017, 2:54pm UTC](https://discuss.elastic.co/t/ubuntu-16-04-ansible-elasticsearch-stuck-at-wait-for-elasticsearch-to-startup/83338/13 "2017-07-11T14:54:13Z")

</div>

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