# ElasticSearch doesn't start after installing 5.6.4

**URL:** <https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444>\
**Category:** Elasticsearch\
**Created:** [November 13, 2017, 5:22pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444 "2017-11-13T17:22:39Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [November 13, 2017, 5:22pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/1 "2017-11-13T17:22:39Z")

</div>

Hello,

I just installed Elasticsearch 5.6.4 from [Download Elasticsearch | Elastic](https://www.elastic.co/downloads/elasticsearch) via DEB (I use Debian 9) package using these commands:

> wget [https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.4.deb](https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.4.deb)  
> dpkg -i elasticsearch-5.6.4.deb  
> apt-get install openjdk-8-jre-headless  
> update-rc.d elasticsearch defaults 95 10  
> service elasticsearch start

But Elasticsearch won't start, this is log:

> ● elasticsearch.service - Elasticsearch  
> Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)  
> Active: failed (Result: exit-code) since Mon 2017-11-13 16:59:24 UTC; 13min ago  
> Docs: [http://www.elastic.co](http://www.elastic.co)  
> Process: 16503 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG\_DIR} -Edefault.path.data=${DATA\_DIR} -Edefault.path.conf=${CONF\_DIR} (code=exited, statu  
> Process: 16500 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)  
> Main PID: 16503 (code=exited, status=1/FAILURE)
> 
> Nov 13 16:59:12 Mysite systemd[1]: Starting Elasticsearch...  
> Nov 13 16:59:12 Mysite systemd[1]: Started Elasticsearch.  
> Nov 13 16:59:24 Mysite systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE  
> Nov 13 16:59:24 Mysite systemd[1]: elasticsearch.service: Unit entered failed state.  
> Nov 13 16:59:24 Mysite systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

But it doesn't say anything useful.

In config file I just changed this:

```
network.host: 51.15.212.76
http.port: 9200
cluster.name: elasticsearch
node.name: "db-master"
node.master: true
node.data: true

```

Where can be a problem?

---

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [November 13, 2017, 9:56pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/2 "2017-11-13T21:56:52Z")

</div>

It is now fixed, because I couldn't bind a address.

---

<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:** [November 13, 2017, 11:19pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/3 "2017-11-13T23:19:27Z")

</div>

Having an internet exposed service of any kind is dangerous. You may want to fix that.

---

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [November 13, 2017, 11:20pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/4 "2017-11-13T23:20:35Z")

</div>

It is for development server.

---

<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:** [November 13, 2017, 11:21pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/5 "2017-11-13T23:21:48Z")

</div>

Why does that make it any less important?

---

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [November 13, 2017, 11:24pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/6 "2017-11-13T23:24:10Z")

</div>

No, but there have access only some people and it is going to be locked by HTTP Auth.

Developers need to have a access to elastic.

---

<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:** [December 11, 2017, 11:24pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-start-after-installing-5-6-4/107444/7 "2017-12-11T23:24:10Z")

</div>

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