# Elasticsearch starts with errors

**URL:** https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451
**Category:** Elasticsearch
**Created:** [June 26, 2015, 6:10pm UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451 "2015-06-26T18:10:01Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![samding](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@samding](https://discuss.elastic.co/u/samding)
#### Post date: [June 26, 2015, 6:10pm UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451/1 "2015-06-26T18:10:01Z")

</div>

Hello,

I downloaded elasticsearch-1.5.1.tar.gz on RHEL 6 on x86.  
When it starts, repeated error msgs like:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/6/6f8d11de7d3914ec192f13ffdaf13960b70672aa.png)

Is this related to configuration? I used Java 7

" java -version  
java version "1.7.0\_65" "

Thanks,

Sam

---

<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: [June 26, 2015, 11:04pm UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451/2 "2015-06-26T23:04:11Z")

</div>

It's much easier to read if you paste the text rather than a screenshot of it.

However if you look at the error it tells you what the problem is `see issue #7210 for details`, that issue is [here](https://github.com/elastic/elasticsearch/pull/7210).

---

<div class="post-metadata">

### Author: ![samding](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@samding](https://discuss.elastic.co/u/samding)
#### Post date: [June 29, 2015, 3:58pm UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451/3 "2015-06-29T15:58:47Z")

</div>

Thank you for your reply.  
But #7200 did not provide a solution. This bug appeared in the previous release (last year),  
now I used the latest release.  
In addition, even though set  
transport.tcp.compress: false  
in elasticsearch.yml, it behaves the same.

Thanks,

---

<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: [June 29, 2015, 9:43pm UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451/4 "2015-06-29T21:43:49Z")

</div>

Did you also set `indices.recovery.compress: false`?

---

<div class="post-metadata">

### Author: ![samding](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@samding](https://discuss.elastic.co/u/samding)
#### Post date: [June 30, 2015, 2:56pm UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451/5 "2015-06-30T14:56:57Z")

</div>

after add "indices.recovery.compress: false", it works.

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: [July 6, 2017, 12:04am UTC](https://discuss.elastic.co/t/elasticsearch-starts-with-errors/24451/6 "2017-07-06T00:04:32Z")

</div>