# Elasticsearch 0.19.8 doesn't initialize, hangs
**URL:** https://discuss.elastic.co/t/elasticsearch-0-19-8-doesnt-initialize-hangs/8379
**Category:** Elasticsearch
**Created:** [July 10, 2012, 6:42pm UTC](https://discuss.elastic.co/t/elasticsearch-0-19-8-doesnt-initialize-hangs/8379 "2012-07-10T18:42:41Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@dev](https://discuss.elastic.co/u/dev)
#### Post date: [July 10, 2012, 6:42pm UTC](https://discuss.elastic.co/t/elasticsearch-0-19-8-doesnt-initialize-hangs/8379/1 "2012-07-10T18:42:41Z")
Elasticsearch hangs after launch and never initializes. This is a
clean install on a clean install of CentOS, chown root:root and chmod
777 to ensure there are no permission issues. There are no error
messages and the only way to stop the app is to force a kill with
"kill -9". Anyone have any experience with this or have any
suggestions? I do have another instance running perfectly fine on
another machine running same os and java version and have been unable
to determine the difference.
java version "1.6.0\_17"
OpenJDK Runtime Environment (IcedTea6 1.7.9) (rhel-1.36.b17.el6\_0-
x86\_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
Elastic Search 0.19.8 (or 0.19.7)
Linux 2.6.32-71.29.1.el6.x86\_64
Output:
[root@nnn]# ../elasticsearch/bin/elasticsearch -f
[2012-07-10 13:26:57,598][INFO][node] [Hrimhari]
{0.19.8}[17939]: initializing ...
[2012-07-10 13:26:57,603][INFO][plugins] [Hrimhari]
loaded [], sites []
[2012-07-10 13:26:57,618][TRACE][env] [Hrimhari]
obtaining node lock on /elasticsearch/data/elasticsearch/nodes/0 ...
[2012-07-10 13:26:57,625][DEBUG][env] [Hrimhari]
using node location [[/elasticsearch/data/elasticsearch/nodes/0]],
local\_node\_id [0]
[2012-07-10 13:26:57,627][TRACE][env] [Hrimhari]
node data locations details: -\> /elasticsearch/data/elasticsearch/
nodes/0, free\_space [60.6gb], usable\_space [60.6gb]
(this is where it hangs)
The running process looks like this:
root 17939 21563 87 13:26 pts/0 00:04:42 /usr/bin/java -Xms256m
-Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -XX:
+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:
+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -
Delasticsearch -Des.foreground=yes -Des.path.home=/elasticsearch -cp 😕
elasticsearch/lib/elasticsearch-0.19.8.jar:/elasticsearch/lib/_😕
elasticsearch/lib/sigar/_ org.elasticsearch.bootstrap.ElasticSearch
---
### Author:  [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [July 10, 2012, 7:27pm UTC](https://discuss.elastic.co/t/elasticsearch-0-19-8-doesnt-initialize-hangs/8379/2 "2012-07-10T19:27:49Z")
Being unable to provide a working solution, I'd like to give my 2c
- consider a very important rule: never ever run applications with user
root. Never. Elasticsearch is no exception, it does not need supervisor
privileges
- it's always a good idea to install a current Java JRE to enjoy resolved
bugs. 1.6.0\_17 is almost three years old
- check if your os network settings (routes, gateway) and mount points are
configured correctly
- remove sigar libraries in order to avoid sigar monitoring hangs
- from the logs ES seems to hang before the node is going to initialize
plugins, so remove all ES plugins, check the classpath (the lib directory
is loaded with \*) and remove unwanted/duplicate jars
Best regards
Jörg
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [July 10, 2012, 7:34pm UTC](https://discuss.elastic.co/t/elasticsearch-0-19-8-doesnt-initialize-hangs/8379/3 "2012-07-10T19:34:27Z")
Agreed, I would try and use a newer JVM version. If it still hangs, install
the Java development package, and run jstack against it and gist the
details? It will tell us where its stuck.
On Tue, Jul 10, 2012 at 9:27 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote:
> Being unable to provide a working solution, I'd like to give my 2c
>
> - consider a very important rule: never ever run applications with user
> root. Never. Elasticsearch is no exception, it does not need supervisor
> privileges
>
> - it's always a good idea to install a current Java JRE to enjoy resolved
> bugs. 1.6.0\_17 is almost three years old
>
> - check if your os network settings (routes, gateway) and mount points are
> configured correctly
>
> - remove sigar libraries in order to avoid sigar monitoring hangs
>
> - from the logs ES seems to hang before the node is going to initialize
> plugins, so remove all ES plugins, check the classpath (the lib directory
> is loaded with \*) and remove unwanted/duplicate jars
>
> Best regards
>
> Jörg
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 3:20am UTC](https://discuss.elastic.co/t/elasticsearch-0-19-8-doesnt-initialize-hangs/8379/4 "2017-07-06T03:20:40Z")