# /etc/init.d/elasticsearch fails at system boot **URL:** \ **Category:** Elasticsearch\ **Created:** [May 6, 2014, 1:12pm UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371 "2014-05-06T13:12:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Zacharie\_Elcor](https://avatars.discourse-cdn.com/v4/letter/z/4491bb/32.png) [@Zacharie\_Elcor](https://discuss.elastic.co/u/Zacharie_Elcor)\ **Post date:** [May 6, 2014, 1:12pm UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371/1 "2014-05-06T13:12:20Z")
Hi, I installed elasticsearch 1.1.1 from rpm package on redhat 6.2 Init script /etc/init.d/elasticsearch is installed and run at server boot but \*no java process is started or _it dies silently. No log in /var/log/elasticsearch/_ but the lock file is touched (/var/lock/subsys/elasticsearch) If I run (as root) "/etc/init.d/elasticsearch start", the node is started. I added a logger statement to /usr/share/elasticsearch/bin/elasticsearch to see what is actually run. Here is what is written to /var/log/message : exec "/usr/bin/java" -Xms4g -Xmx4g -Xss256k -Djava.awt.headless=true -XX:+ UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly - XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid -Des. path.home="/usr/share/elasticsearch" -cp ":/usr/share/elasticsearch/lib/elasticsearch-1.1.1.jar:/usr/share/elasticsearch/lib/_:/usr/share/elasticsearch/lib/sigar/_" -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/ log/elasticsearch -Des.default.path.data=/var/product/elasticsearch -Des.default.path.work= /tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch org.elasticsearch.bootstrap.Elasticsearch If I run manually this command line after switching to elasticsearch user, the node is started. In summary, everything works normally except that elasticsearch won't start automatically after a server reboot. Any clue ? I'm stuck -- Zac -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [May 6, 2014, 1:24pm UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371/2 "2014-05-06T13:24:55Z")
I had trouble with this a while ago and in my case it turned out to be that I didn't have enough ram to allocate and the JDK was crashing. That probably isn't what is up with yours but you can follow along with the issue starting here: > > > I was trying to test some changes on a virtual machine that didn't have enough r…am to start Elasticsearch in the configuration I had it set in but didn't see the error messages because the init script just died: > > \`\`\` > \* Starting ElasticSearch Server > \`\`\` > > Starting Elasticsearch manually using the same configuration spat out the helpful: > > \`\`\` > OpenJDK 64-Bit Server VM warning: INFO: os::commit\_memory(0x000000077ad30000, 2060255232, 0) failed; error='Cannot allocate memory' (errno=12) > \# > \# There is insufficient memory for the Java Runtime Environment to continue. > \# Native memory allocation (malloc) failed to allocate 2060255232 bytes for committing reserved memory. > \# An error report file with more information is saved as: > \# /tmp/hs\_err\_pid8570.log > \`\`\` > > It'd be nice to be able to read that message if it fails to start via the init script. These kinds of problems irk me because I don't really have a good way to solve them. Maybe pipe the stdout/stderr of the Elasticsearch process in the init script to tmp temporarily file then try to start it. The JDK has a habit of printing errors to stderr because, when it fails, it doesn't have anywhere else to send them. Path problems, maybe? Nik On Tue, May 6, 2014 at 9:12 AM, Zacharie Elcor [zelcor@gmail.com](mailto:zelcor@gmail.com) wrote: > Hi, > > I installed elasticsearch 1.1.1 from rpm package on redhat 6.2 > > Init script /etc/init.d/elasticsearch is installed and run at server boot > but \*no java process is started or _it dies silently. No log in > /var/log/elasticsearch/_ but the lock file is touched > (/var/lock/subsys/elasticsearch) > > If I run (as root) "/etc/init.d/elasticsearch start", the node is started. > > I added a logger statement to /usr/share/elasticsearch/bin/elasticsearch > to see what is actually run. Here is what is written to /var/log/message : > > exec "/usr/bin/java" -Xms4g -Xmx4g -Xss256k -Djava.awt.headless=true -XX > :+UseParNewGC -XX:+UseConcMarkSweepGC > -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly > -XX:+HeapDumpOnOutOfMemoryError > -Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid - > Des.path.home="/usr/share/elasticsearch" > -cp > ":/usr/share/elasticsearch/lib/elasticsearch-1.1.1.jar:/usr/share/elasticsearch/lib/_:/usr/share/elasticsearch/lib/sigar/_" > -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs= > /var/log/elasticsearch > -Des.default.path.data=/var/product/elasticsearch -Des.default.path.work= > /tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch > org.elasticsearch.bootstrap.Elasticsearch > > If I run manually this command line after switching to elasticsearch user, > the node is started. > > In summary, everything works normally except that elasticsearch won't > start automatically after a server reboot. > > Any clue ? I'm stuck > > -- > Zac > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2YdtC3tJtvhhuizRLSgJE8qTh8aUW%2Bz9\_a-daEWmd%3DkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2YdtC3tJtvhhuizRLSgJE8qTh8aUW%2Bz9_a-daEWmd%3DkQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Zacharie\_Elcor](https://avatars.discourse-cdn.com/v4/letter/z/4491bb/32.png) [@Zacharie\_Elcor](https://discuss.elastic.co/u/Zacharie_Elcor)\ **Post date:** [May 7, 2014, 9:54am UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371/3 "2014-05-07T09:54:17Z")
Many thanks Nik. Not a RAM issue but your second advice was helpful. I added "\> /tmp/logfile 2\>&1" at the end of line "daemon --user..." in /etc/init.d/elasticsearch. After rebbot, /tmp/logfile contained a message saying that env var HOSTNAME was not defined. In my case, HOSTNAME is used in elasticsearch.yml to define node name. So the rule seems to be : If you make use of environment variables in elasticsearch.yml (as explained in [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html#styles)), make sure these var are defined when the service starts. -- Zac On Tuesday, May 6, 2014 3:24:55 PM UTC+2, Nikolas Everett wrote: > I had trouble with this a while ago and in my case it turned out to be > that I didn't have enough ram to allocate and the JDK was crashing. That > probably isn't what is up with yours but you can follow along with the > issue starting here: > [Init script should allow the user to investigate stdout and stderr if initializing fails · Issue #5234 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/5234) > > These kinds of problems irk me because I don't really have a good way to > solve them. Maybe pipe the stdout/stderr of the Elasticsearch process in > the init script to tmp temporarily file then try to start it. The JDK has > a habit of printing errors to stderr because, when it fails, it doesn't > have anywhere else to send them. > > Path problems, maybe? > > Nik > > On Tue, May 6, 2014 at 9:12 AM, Zacharie Elcor \<[zel...@gmail.com](mailto:zel...@gmail.com)\ > > > wrote: > > > Hi, > > > > I installed elasticsearch 1.1.1 from rpm package on redhat 6.2 > > > > Init script /etc/init.d/elasticsearch is installed and run at server boot > > but \*no java process is started or _it dies silently. No log in > > /var/log/elasticsearch/_ but the lock file is touched > > (/var/lock/subsys/elasticsearch) > > > > If I run (as root) "/etc/init.d/elasticsearch start", the node is started. > > > > I added a logger statement to /usr/share/elasticsearch/bin/elasticsearch > > to see what is actually run. Here is what is written to /var/log/message : > > > > exec "/usr/bin/java" -Xms4g -Xmx4g -Xss256k -Djava.awt.headless=true -XX > > :+UseParNewGC -XX:+UseConcMarkSweepGC > > -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly > > -XX:+HeapDumpOnOutOfMemoryError > > -Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid - > > Des.path.home="/usr/share/elasticsearch" > > -cp > > ":/usr/share/elasticsearch/lib/elasticsearch-1.1.1.jar:/usr/share/elasticsearch/lib/_:/usr/share/elasticsearch/lib/sigar/_" > > -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs= > > /var/log/elasticsearch > > -Des.default.path.data=/var/product/elasticsearch -Des.default.path.work > > =/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch > > org.elasticsearch.bootstrap.Elasticsearch > > > > If I run manually this command line after switching to elasticsearch > > user, the node is started. > > > > In summary, everything works normally except that elasticsearch won't > > start automatically after a server reboot. > > > > Any clue ? I'm stuck > > > > -- > > Zac > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/960cd129-0226-4395-9a2e-64f19113baba%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/960cd129-0226-4395-9a2e-64f19113baba%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [May 7, 2014, 10:01am UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371/4 "2014-05-07T10:01:17Z")
What is the actual variable you used in your yml? Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 7 May 2014 19:54, Zacharie Elcor [zelcor@gmail.com](mailto:zelcor@gmail.com) wrote: > Many thanks Nik. Not a RAM issue but your second advice was helpful. > > I added "\> /tmp/logfile 2\>&1" at the end of line "daemon --user..." in > /etc/init.d/elasticsearch. > > After rebbot, /tmp/logfile contained a message saying that env var > HOSTNAME was not defined. In my case, HOSTNAME is used in elasticsearch.yml > to define node name. > > So the rule seems to be : If you make use of environment variables in > elasticsearch.yml (as explained in > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html#styles)), > make sure these var are defined when the service starts. > > -- > Zac > > On Tuesday, May 6, 2014 3:24:55 PM UTC+2, Nikolas Everett wrote: > > > I had trouble with this a while ago and in my case it turned out to be > > that I didn't have enough ram to allocate and the JDK was crashing. That > > probably isn't what is up with yours but you can follow along with the > > issue starting here: [GitHub - elastic/elasticsearch: Free and Open, Distributed, RESTful Search Engine](https://github.com/elasticsearch/elasticsearch/) > > issues/5234 > > > > These kinds of problems irk me because I don't really have a good way to > > solve them. Maybe pipe the stdout/stderr of the Elasticsearch process in > > the init script to tmp temporarily file then try to start it. The JDK has > > a habit of printing errors to stderr because, when it fails, it doesn't > > have anywhere else to send them. > > > > Path problems, maybe? > > > > Nik > > > > On Tue, May 6, 2014 at 9:12 AM, Zacharie Elcor [zel...@gmail.com](mailto:zel...@gmail.com) wrote: > > > > > Hi, > > > > > > I installed elasticsearch 1.1.1 from rpm package on redhat 6.2 > > > > > > Init script /etc/init.d/elasticsearch is installed and run at server > > > boot but \*no java process is started or _it dies silently. No log in > > > /var/log/elasticsearch/_ but the lock file is touched (/var/lock/subsys/ > > > elasticsearch) > > > > > > If I run (as root) "/etc/init.d/elasticsearch start", the node is > > > started. > > > > > > I added a logger statement to /usr/share/elasticsearch/bin/elasticsearch > > > to see what is actually run. Here is what is written to /var/log/message : > > > > > > exec "/usr/bin/java" -Xms4g -Xmx4g -Xss256k -Djava.awt.headless=true - > > > XX:+UseParNewGC -XX:+UseConcMarkSweepGC > > > -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancy > > > Only -XX:+HeapDumpOnOutOfMemoryError > > > -Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid - > > > Des.path.home="/usr/share/elasticsearch" > > > -cp ":/usr/share/elasticsearch/lib/elasticsearch-1.1.1.jar:/ > > > usr/share/elasticsearch/lib/_:/usr/share/elasticsearch/lib/sigar/_" - > > > Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs= > > > /var/log/elasticsearch > > > -Des.default.path.data=/var/product/elasticsearch -Des.default.path. > > > work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch > > > org.elasticsearch.bootstrap.Elasticsearch > > > > > > If I run manually this command line after switching to elasticsearch > > > user, the node is started. > > > > > > In summary, everything works normally except that elasticsearch won't > > > start automatically after a server reboot. > > > > > > Any clue ? I'm stuck > > > > > > -- > > > Zac > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2% > > > [40googlegroups.com](http://40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1b462c05-d03a-4283-b8a4-b84f37f01cc2%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/960cd129-0226-4395-9a2e-64f19113baba%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/960cd129-0226-4395-9a2e-64f19113baba%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/960cd129-0226-4395-9a2e-64f19113baba%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/960cd129-0226-4395-9a2e-64f19113baba%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624aDbKauX%3DBDY6QWNcs5EAH%3DZ6Z8e9NC\_W5qykezMY\_qng%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624aDbKauX%3DBDY6QWNcs5EAH%3DZ6Z8e9NC_W5qykezMY_qng%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Zacharie\_Elcor](https://avatars.discourse-cdn.com/v4/letter/z/4491bb/32.png) [@Zacharie\_Elcor](https://discuss.elastic.co/u/Zacharie_Elcor)\ **Post date:** [May 7, 2014, 5:57pm UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371/5 "2014-05-07T17:57:55Z")
node.name: node.${HOSTNAME} On Wednesday, May 7, 2014 12:01:17 PM UTC+2, Mark Walkom wrote: > What is the actual variable you used in your yml? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/38746dda-0c16-48a0-9cc8-ed6bfd70230e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/38746dda-0c16-48a0-9cc8-ed6bfd70230e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:31am UTC](https://discuss.elastic.co/t/etc-init-d-elasticsearch-fails-at-system-boot/17371/6 "2017-07-06T01:31:00Z")