# Elasticsearch is starting two processes at boot **URL:** \ **Category:** Elasticsearch\ **Created:** [July 26, 2012, 10:57am UTC](https://discuss.elastic.co/t/elasticsearch-is-starting-two-processes-at-boot/8523 "2012-07-26T10:57:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dsj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dsj/32/2794_2.png) [@dsj](https://discuss.elastic.co/u/dsj)\ **Post date:** [July 26, 2012, 10:57am UTC](https://discuss.elastic.co/t/elasticsearch-is-starting-two-processes-at-boot/8523/1 "2012-07-26T10:57:02Z")
Hi everyone, Without any apparent reason elasticsearch starts two processes at boot. I re-instaled the service to run at boot and nothing changed. This started to happen when i ran elasticsearch the command, "bin/elasticsearch -f -Des.max-open-files=true". Elasticsearch version: 0.19.2 root 4491 0.0 0.0 74480 1280 ? Sl 11:41 0:00 /[somePath]/elasticsearch-0.19.2/bin/service/exec/elasticsearch-linux-x86-64 /[somePath]/elasticsearch-0.19.2/bin/service/elasticsearch.conf wrapper.syslog.ident=elasticsearch wrapper.pidfile=/[somePath]/elasticsearch-0.19.2/bin/service/././elasticsearch.pid wrapper.name=elasticsearch wrapper.displayname=ElasticSearch wrapper.daemonize=TRUE wrapper.statusfile=/[somePath]/elasticsearch-0.19.2/bin/service/././elasticsearch.status wrapper.java.statusfile=/[somePath]/elasticsearch-0.19.2/bin/service/././elasticsearch.java.status wrapper.lockfile=/var/lock/subsys/elasticsearch root 4493 41.9 8.3 8058880 1355816 ? Sl 11:41 1:21 java -Delasticsearch-service -Des-foreground=yes -Des.path.home=/[somePath]/elasticsearch-0.19.2 -Djline.enabled=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Des.max-open-files=true -Xms2048m -Xmx7168m -Djava.library.path=/[somePath]/elasticsearch-0.19.2/bin/service/lib -classpath /[somePath]/elasticsearch-0.19.2/bin/service/lib/wrapper.jar:/[somePath]/elasticsearch-0.19.2/lib/elasticsearch-0.19.2.jar:/[somePath]/elasticsearch-0.19.2/lib/jna-3.3.0.jar:/[somePath]/elasticsearch-0.19.2/lib/log4j-1.2.16.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-analyzers-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-core-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-highlighter-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-memory-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-queries-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/sigar/sigar-1.6.4.jar -Dwrapper.key=S3fwTFClfvlzwdPE -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.disable\_console\_input=TRUE -Dwrapper.pid=4491 -Dwrapper.version=3.5.6 -Dwrapper.native\_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.elasticsearch.bootstrap.Bootstrap Why is this happening and how to fix this? Regards ---
**Author:** ![Rafal\_Kuc\_3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafal_kuc_3/32/799_2.png) [@Rafal\_Kuc\_3](https://discuss.elastic.co/u/Rafal_Kuc_3)\ **Post date:** [July 26, 2012, 11:02am UTC](https://discuss.elastic.co/t/elasticsearch-is-starting-two-processes-at-boot/8523/2 "2012-07-26T11:02:22Z")
Hello! If you are using wrapper than this is normal behavior. But then, you shouldn't run ElasticSearch with bin/elasticsearch script, but you should have the /etc/init.d/elasticsearch which should point to the wrapper startup script. _--_ Regards, Rafał Kuć Sematext :: [http://sematext.com/](http://sematext.com/) _:: Solr - Lucene - Nutch - ElasticSearch_ Hi everyone, Without any apparent reason elasticsearch starts two processes at boot. I re-instaled the service to run at boot and nothing changed. This started to happen when i ran elasticsearch the command, "bin/elasticsearch -f -Des.max-open-files=true". Elasticsearch version: 0.19.2 root 4491 0.0 0.0 74480 1280 ? Sl 11:41 0:00 /[somePath]/elasticsearch-0.19.2/bin/service/exec/elasticsearch-linux-x86-64 /[somePath]/elasticsearch-0.19.2/bin/service/elasticsearch.conf wrapper.syslog.ident=elasticsearch wrapper.pidfile=/[somePath]/elasticsearch-0.19.2/bin/service/././elasticsearch.pid wrapper.name=elasticsearch wrapper.displayname=ElasticSearch wrapper.daemonize=TRUE wrapper.statusfile=/[somePath]/elasticsearch-0.19.2/bin/service/././elasticsearch.status wrapper.java.statusfile=/[somePath]/elasticsearch-0.19.2/bin/service/././elasticsearch.java.status wrapper.lockfile=/var/lock/subsys/elasticsearch root 4493 41.9 8.3 8058880 1355816 ? Sl 11:41 1:21 java -Delasticsearch-service -Des-foreground=yes -Des.path.home=/[somePath]/elasticsearch-0.19.2 -Djline.enabled=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Des.max-open-files=true -Xms2048m -Xmx7168m -Djava.library.path=/[somePath]/elasticsearch-0.19.2/bin/service/lib -classpath /[somePath]/elasticsearch-0.19.2/bin/service/lib/wrapper.jar:/[somePath]/elasticsearch-0.19.2/lib/elasticsearch-0.19.2.jar:/[somePath]/elasticsearch-0.19.2/lib/jna-3.3.0.jar:/[somePath]/elasticsearch-0.19.2/lib/log4j-1.2.16.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-analyzers-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-core-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-highlighter-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-memory-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/lucene-queries-3.5.0.jar:/[somePath]/elasticsearch-0.19.2/lib/sigar/sigar-1.6.4.jar -Dwrapper.key=S3fwTFClfvlzwdPE -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.disable\_console\_input=TRUE -Dwrapper.pid=4491 -Dwrapper.version=3.5.6 -Dwrapper.native\_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.elasticsearch.bootstrap.Bootstrap Why is this happening and how to fix this? Regards ---
**Author:** ![dsj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dsj/32/2794_2.png) [@dsj](https://discuss.elastic.co/u/dsj)\ **Post date:** [July 26, 2012, 11:16am UTC](https://discuss.elastic.co/t/elasticsearch-is-starting-two-processes-at-boot/8523/3 "2012-07-26T11:16:53Z")
Hey, Thanks for the answer, I was unaware of the fact that you just mentioned which was causing me some confusion. Greets ---
**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, 3:18am UTC](https://discuss.elastic.co/t/elasticsearch-is-starting-two-processes-at-boot/8523/4 "2017-07-06T03:18:56Z")