# Elasticsearch not starting up - ES 1.7/2.1 RHEL 6.4

**URL:** <https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222>\
**Category:** Elasticsearch\
**Created:** [December 15, 2015, 9:33am UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222 "2015-12-15T09:33:20Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![asatsi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asatsi/32/28417_2.png) [@asatsi](https://discuss.elastic.co/u/asatsi)\
**Post date:** [December 15, 2015, 9:33am UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/1 "2015-12-15T09:33:20Z")

</div>

This is rather strange. It was working fine. But now it just doesn't get started and is stuck at  
[2015-12-15 14:57:25,021][INFO][node] [Vertigo] initializing ...  
[2015-12-15 14:57:25,079][INFO][plugins] [Vertigo] loaded [], sites []

Then I tried getting ES 2.1. But it just doesn't throw any logs at all and is completely stuck. I am unable to figure out what's wrong. Any ideas?

---

<div class="post-metadata">

**Author:** ![asatsi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asatsi/32/28417_2.png) [@asatsi](https://discuss.elastic.co/u/asatsi)\
**Post date:** [December 15, 2015, 12:47pm UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/2 "2015-12-15T12:47:33Z")

</div>

Figured out that "df" was stuck due to stale NFS mount causing this unwarranted behaviour. I guess ES must be trying to figure out the high/low disk watermarks prior to start-up.

---

<div class="post-metadata">

**Author:** ![rclarke](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rclarke/32/68604_2.png) [@rclarke](https://discuss.elastic.co/u/rclarke)\
**Post date:** [December 15, 2015, 4:07pm UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/3 "2015-12-15T16:07:31Z")

</div>

Hello Satish,

There are other issues around using Elasticsearch on NFS as well - it is not recommended to use Elasticserach on NFS.

Cheers,  
-Robin-

---

<div class="post-metadata">

**Author:** ![asatsi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asatsi/32/28417_2.png) [@asatsi](https://discuss.elastic.co/u/asatsi)\
**Post date:** [December 16, 2015, 5:37am UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/4 "2015-12-16T05:37:28Z")

</div>

No no Robin, I am not using NFS for storing indices but the machine has NFS mounts which are not being used by ES at all. However I suspect it tries to do a "df" kind of operation where it got stuck!

---

<div class="post-metadata">

**Author:** ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)\
**Post date:** [December 16, 2015, 11:01am UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/5 "2015-12-16T11:01:56Z")

</div>

Hi, can you post the full stack trace for the hung thread?

"kill -QUIT pid" should show it, where pid is the process ID of the Elasticsearch java process.

Thanks.

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [December 16, 2015, 11:30am UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/6 "2015-12-16T11:30:16Z")

</div>

As a side node, please use `bg,intr,soft` mount option in `/etc/fstab` or when mounting NFS manually.

ES is indeed calling JVM file system services that list all mounted file systems, which is similar to `df`. By default, mounted NFS volumes, once they got stale, wait indefinitely for I/O.

When mounted with `soft` option, I/O requests on stale NFS mounts will timeout.

`bg` spins off a background retry task at mount time so NFS mounts do not block the OS to boot.

`intr` makes the programs who perform I/O requests on a stale NFS mount interruptible, e.g. by `kill`

---

<div class="post-metadata">

**Author:** ![asatsi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asatsi/32/28417_2.png) [@asatsi](https://discuss.elastic.co/u/asatsi)\
**Post date:** [December 17, 2015, 8:31am UTC](https://discuss.elastic.co/t/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/7 "2015-12-17T08:31:33Z")

</div>

Excellent, thanks Jorg!

---

<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/elasticsearch-not-starting-up-es-1-7-2-1-rhel-6-4/37222/8 "2017-07-05T23:30:19Z")

</div>


