# ./bin/elasticsearch -version kills any running elasticsearch

**URL:** <https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822>\
**Category:** Elasticsearch\
**Created:** [November 15, 2018, 9:38am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822 "2018-11-15T09:38:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\
**Post date:** [November 15, 2018, 9:38am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822/1 "2018-11-15T09:38:29Z")

</div>

From elasticsearch-6.4.3, if we run ./bin/elasticsearch -version any running elasticsearch instance seems to be killed with -9. This does did not happen before this version. We are performing a version check before update to prevent older or the same version to be installed by mistake.

Earlier, this worked and the flag was --version instead BUT we get this problem even with --version

/Johan

---

<div class="post-metadata">

**Author:** ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)\
**Post date:** [November 15, 2018, 10:02am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822/2 "2018-11-15T10:02:09Z")

</div>

@JohanRask, you can use the below command to check the version of elasticsearch:

```auto
curl 'http://Your_Elasticserach_server_IP:9200'

```

Thanks.

---

<div class="post-metadata">

**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\
**Post date:** [November 15, 2018, 10:04am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822/3 "2018-11-15T10:04:06Z")

</div>

True, we actually use that as well after install...  
But it still does not make any sense to kill a running instance.

---

<div class="post-metadata">

**Author:** ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)\
**Post date:** [November 15, 2018, 10:10am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822/4 "2018-11-15T10:10:43Z")

</div>

@JohanRask, i didn't use Elasticsearch6.4.2 or higher version. So i need to install it to replicate the issue.

Thanks.

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [November 15, 2018, 10:33am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822/5 "2018-11-15T10:33:11Z")

</div>

I can't reproduce this:

```auto
$ curl -u elastic:${ELASTIC_PASSWORD} 'http://localhost:9200?pretty' --silent | jq .version.number
"6.4.3"
$ ./bin/elasticsearch -version
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Version: 6.4.3, Build: default/tar/fe40335/2018-10-30T23:17:19.084789Z, JVM: 11
$ curl -u elastic:${ELASTIC_PASSWORD} 'http://localhost:9200?pretty' --silent | jq .version.number
"6.4.3"

```

Can you provide more details about your local setup and the precise symptoms you're seeing (log messages, etc).

---

<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 13, 2018, 10:37am UTC](https://discuss.elastic.co/t/bin-elasticsearch-version-kills-any-running-elasticsearch/156822/6 "2018-12-13T10:37:01Z")

</div>

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