# All commands in the elasticsearch-2.1.0/bin directory hang silently on RHEL 7

**URL:** <https://discuss.elastic.co/t/all-commands-in-the-elasticsearch-2-1-0-bin-directory-hang-silently-on-rhel-7/36089>\
**Category:** Elasticsearch\
**Created:** [December 1, 2015, 7:43pm UTC](https://discuss.elastic.co/t/all-commands-in-the-elasticsearch-2-1-0-bin-directory-hang-silently-on-rhel-7/36089 "2015-12-01T19:43:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gstipton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gstipton/32/6310_2.png) [@gstipton](https://discuss.elastic.co/u/gstipton)\
**Post date:** [December 1, 2015, 7:43pm UTC](https://discuss.elastic.co/t/all-commands-in-the-elasticsearch-2-1-0-bin-directory-hang-silently-on-rhel-7/36089/1 "2015-12-01T19:43:47Z")

</div>

I'm working on an upgrade from 1.6.0 to 2.1.0. This is on RHEL 7 and Java 1.8.0\_40.

The issue is that when I execute any command in the elasticsearch-2.1.0/bin directory (elasticsearch, plugin, etc.), it just hangs indefinitely. There is no log or console output. However, if I switch to the elasticsearch-1.6.0 directory and execute any command, it works fine.

If I unpack the same 2.1.0 tar file on my Mac and execute a command, it also works fine. It appears to be an issue specific to RHEL 7 and elasticsearch 2.1.0.

I feel like I must be missing something, but I'm not sure where to go with this. Any ideas?

Thanks.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [December 1, 2015, 7:59pm UTC](https://discuss.elastic.co/t/all-commands-in-the-elasticsearch-2-1-0-bin-directory-hang-silently-on-rhel-7/36089/2 "2015-12-01T19:59:03Z")

</div>

> [@gstipton](#):
>
> I feel like I must be missing something, but I'm not sure where to go with this. Any ideas?

Its kind of hard to tell. We test the rpm and tar on RHEL 7 as part of the build so I don't expect it to be broken in general. I'd try to debug this starting with running `bin/plugin`, watching it hang, and then:

1. Check what elasticsearch stuff is running with `ps aux`.
2. Get a stack trace from the Java process with `jstack`. There might be a smoking gun there.

---

<div class="post-metadata">

**Author:** ![gstipton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gstipton/32/6310_2.png) [@gstipton](https://discuss.elastic.co/u/gstipton)\
**Post date:** [December 16, 2015, 6:04pm UTC](https://discuss.elastic.co/t/all-commands-in-the-elasticsearch-2-1-0-bin-directory-hang-silently-on-rhel-7/36089/3 "2015-12-16T18:04:50Z")

</div>

Thanks for the response, and sorry for the delay. It ended up being a mounted filesystem that died - unrelated to ElasticSearch. We're running 2.1 and all is well.

---

<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 5, 2017, 11:30pm UTC](https://discuss.elastic.co/t/all-commands-in-the-elasticsearch-2-1-0-bin-directory-hang-silently-on-rhel-7/36089/4 "2017-07-05T23:30:29Z")

</div>

Closed on July 5, 2017, 11:30pm UTC