# Your distribution is broken

**URL:** <https://discuss.elastic.co/t/your-distribution-is-broken/206638>\
**Category:** Elasticsearch\
**Created:** [November 5, 2019, 3:58pm UTC](https://discuss.elastic.co/t/your-distribution-is-broken/206638 "2019-11-05T15:58:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pditommaso](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pditommaso/32/57193_2.png) [@pditommaso](https://discuss.elastic.co/u/pditommaso)\
**Post date:** [November 5, 2019, 3:58pm UTC](https://discuss.elastic.co/t/your-distribution-is-broken/206638/1 "2019-11-05T15:58:26Z")

</div>

Running Elasticsearch with the following command

```
docker run -d --name elasticsearch --rm --name es -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" elasticsearch:6.8.4

```

I'm getting the following error on a basic `INFO` API request:

```
java.io.IOException: Unable to parse response body for Response{requestLine=GET / HTTP/1.1, host=http://localhost:9200, response=HTTP/1.1 200 OK}

    at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1275)
    at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1231)
    at org.elasticsearch.client.RestHighLevelClient.info(RestHighLevelClient.java:393)
    at io.test.ElasticTest.should get info(ElasticTest.groovy:40)
Caused by: org.elasticsearch.common.xcontent.XContentParseException: [15:3] [org.elasticsearch.action.main.MainResponse] failed to parse field [version]
    at org.elasticsearch.common.xcontent.ObjectParser.parseValue(ObjectParser.java:316)
    at org.elasticsearch.common.xcontent.ObjectParser.parseSub(ObjectParser.java:326)
    at org.elasticsearch.common.xcontent.ObjectParser.parse(ObjectParser.java:168)
    at org.elasticsearch.common.xcontent.ObjectParser.apply(ObjectParser.java:182)
    at org.elasticsearch.action.main.MainResponse.fromXContent(MainResponse.java:150)
    at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1406)
    at org.elasticsearch.client.RestHighLevelClient.lambda$performRequestAndParseEntity$9(RestHighLevelClient.java:1232)
    at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1273)
    ... 3 more
Caused by: java.lang.IllegalStateException: unexpected distribution type [docker]; your distribution is broken
    at org.elasticsearch.Build$Type.fromDisplayName(Build.java:106)
    at org.elasticsearch.action.main.MainResponse.lambda$static$4(MainResponse.java:140)
    at org.elasticsearch.common.xcontent.ObjectParser.lambda$declareField$1(ObjectParser.java:213)
    at org.elasticsearch.common.xcontent.ObjectParser.parseValue(ObjectParser.java:314)

```

Any clue what's wrong?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 5, 2019, 7:09pm UTC](https://discuss.elastic.co/t/your-distribution-is-broken/206638/2 "2019-11-05T19:09:58Z")

</div>

welcome!

What is the client version you are using?

---

<div class="post-metadata">

**Author:** ![pditommaso](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pditommaso/32/57193_2.png) [@pditommaso](https://discuss.elastic.co/u/pditommaso)\
**Post date:** [November 5, 2019, 7:55pm UTC](https://discuss.elastic.co/t/your-distribution-is-broken/206638/3 "2019-11-05T19:55:50Z")

</div>

Hi David, I've solved upgrading the client to the same version as Elasticsearch server. thanks!

---

<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 3, 2019, 7:55pm UTC](https://discuss.elastic.co/t/your-distribution-is-broken/206638/4 "2019-12-03T19:55:56Z")

</div>

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