# Unable to start ElasticSearch after install on CENTOS 7 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 4, 2020, 2:41pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733 "2020-08-04T14:41:03Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![ian-hosting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ian-hosting/32/73300_2.png) [@ian-hosting](https://discuss.elastic.co/u/ian-hosting)\ **Post date:** [August 4, 2020, 2:41pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/1 "2020-08-04T14:41:03Z")
Hi Went through the steps to install the latest ElasticSearch via rpm and all seemed to go well but when I try to start it, there is an error First time attempting to install this so am a bit lost as to where to look for what is causing the problem and all help gratefully received Thanks Ian ```auto # systemctl -l status elasticsearch ● elasticsearch.service - Elasticsearch Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-08-04 12:00:32 BST; 3h 35min ago Docs: https://www.elastic.co Process: 32721 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE) Main PID: 32721 (code=exited, status=1/FAILURE) Aug 04 12:00:31 server.domain.co.uk systemd-entrypoint[32721]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) Aug 04 12:00:31 server.domain.co.uk systemd-entrypoint[32721]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) Aug 04 12:00:31 server.domain.co.uk systemd-entrypoint[32721]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) Aug 04 12:00:31 server.domain.co.uk systemd-entrypoint[32721]: at org.elasticsearch.cli.Command.main(Command.java:90) Aug 04 12:00:31 server.domain.co.uk systemd-entrypoint[32721]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) Aug 04 12:00:31 server.domain.co.uk systemd-entrypoint[32721]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) Aug 04 12:00:32 server.domain.co.uk systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE Aug 04 12:00:32 server.domain.co.uk systemd[1]: Failed to start Elasticsearch. Aug 04 12:00:32 server.domain.co.uk systemd[1]: Unit elasticsearch.service entered failed state. Aug 04 12:00:32 server.domain.co.uk systemd[1]: elasticsearch.service failed. ``` ---
**Author:** ![ian-hosting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ian-hosting/32/73300_2.png) [@ian-hosting](https://discuss.elastic.co/u/ian-hosting)\ **Post date:** [August 4, 2020, 3:50pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/2 "2020-08-04T15:50:40Z")
As a test, I followed the exact same procedure on another server (that should be configured identically) and it worked perfectly. Relevant information from journalctr Any other pointers please ? ```auto Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.systemd.Libsystemd.lambda$static$0(Libsystemd.java:34) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.systemd.Libsystemd.(Libsystemd.java:33) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.systemd.SystemdPlugin.sd_notify(SystemdPlugin.java:126) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.systemd.SystemdPlugin.onNodeStarted(SystemdPlugin.java:137) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.node.Node.start(Node.java:823) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:317) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:402) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.cli.Command.main(Command.java:90) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) Aug 04 16:45:09 server.domain.co.uk systemd-entrypoint[17950]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) Aug 04 16:45:10 server.domain.co.uk systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE Aug 04 16:45:10 server.domain.co.uk systemd[1]: Unit elasticsearch.service entered failed state. Aug 04 16:45:10 server.domain.co.uk systemd[1]: elasticsearch.service failed ``` ---
**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\ **Post date:** [August 5, 2020, 4:51am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/3 "2020-08-05T04:51:41Z")
No idea; need to find more logs of some type or find way to start manually, etc. as must be some core issue wrong with JVM or disk/network, etc. Kinda strange, though usually good at showing errors. ---
**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\ **Post date:** [August 5, 2020, 4:52am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/4 "2020-08-05T04:52:01Z")
Not SELinux? Have disk space, etc.? ---
**Author:** ![ian-hosting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ian-hosting/32/73300_2.png) [@ian-hosting](https://discuss.elastic.co/u/ian-hosting)\ **Post date:** [August 5, 2020, 5:50am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/5 "2020-08-05T05:50:42Z")
Hi Steve Thanks for your replies - SELinux is disabled and plenty of disk space. Happy to provide extracts from any other logs - are there any you would recommend ? Thanks Ian ---
**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\ **Post date:** [August 5, 2020, 7:44am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/6 "2020-08-05T07:44:09Z")
Not really, all I can think of are the base elasticsearch logs - I guess to figure out if it's really starting at all, or some JVM issues prevent that - something has to be different, maybe Java version or Java on one VM but not other (ES V7 has its own JVM but maybe it's interfered with or HOME set wrong, etc.) Need to find the STDERR logs or output, see below. But looking at your logs, it's failing in bootstrap which checks some things like host, IP, config, shared RAM, etc. so must be failing that, just no logs. Looking at the code for the lines it mentions, in latest version, it can't seem to create / setup the process, or can't daemonize: org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) init(daemonize, pidFile, quiet, env); But if that fails, should show an error message from this exception which it must be hitting and then dying; throw new UserException(ExitCodes.CONFIG, e.getMessage()); The real init code is here and complex, but stderr should show fatal startup errors, and can fail for many reasons so need to find that stderr - even if you need to start manually on command line; should be easy. > ---
**Author:** ![ian-hosting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ian-hosting/32/73300_2.png) [@ian-hosting](https://discuss.elastic.co/u/ian-hosting)\ **Post date:** [August 5, 2020, 9:33am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/7 "2020-08-05T09:33:48Z")
The installed versions of Java are exactly the same across both servers so doesnt look like that. > [@Steve\_Mushero](#): > > The real init code is here and complex, but stderr should show fatal startup errors, and can fail for many reasons so need to find that stderr - even if you need to start manually on command line; should be easy. Can you please explain the procedure ? The only thing I have found from any of the standard logs is the following extract from elasticsearch.log ```auto [2020-08-04T16:45:09,690][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [server.domain.co.uk] fatal error in thread [main], exiting java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native at org.elasticsearch.systemd.Libsystemd.lambda$static$0(Libsystemd.java:34) ~[?:?] at java.security.AccessController.doPrivileged(AccessController.java:312) ~[?:?] at org.elasticsearch.systemd.Libsystemd.(Libsystemd.java:33) ~[?:?] at org.elasticsearch.systemd.SystemdPlugin.sd_notify(SystemdPlugin.java:126) ~[?:?] at org.elasticsearch.systemd.SystemdPlugin.onNodeStarted(SystemdPlugin.java:137) ~[?:?] at java.util.ArrayList.forEach(ArrayList.java:1510) ~[?:?] at org.elasticsearch.node.Node.start(Node.java:823) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:317) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:402) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) ~[elasticsearch-cli-7.8.1.jar:7.8.1] at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.8.1.jar:7.8.1] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) ~[elasticsearch-7.8.1.jar:7.8.1] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.8.1.jar:7.8.1] ``` ---
**Author:** ![d.silwon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d.silwon/32/65853_2.png) [@d.silwon](https://discuss.elastic.co/u/d.silwon)\ **Post date:** [August 5, 2020, 10:33am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/8 "2020-08-05T10:33:58Z")
Can you show us the tmp directory from file /etc/elasticsearch/jvm.options and section "## JVM temporary directory"? ---
**Author:** ![ian-hosting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ian-hosting/32/73300_2.png) [@ian-hosting](https://discuss.elastic.co/u/ian-hosting)\ **Post date:** [August 5, 2020, 11:29am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/9 "2020-08-05T11:29:44Z")
Thanks for your input ! ```auto ## JVM temporary directory -Djava.io.tmpdir=${ES_TMPDIR} ``` Same for both servers > [@d.silwon](#): > > Can you show us the tmp directory from file /etc/elasticsearch/jvm.options Are you asking for something different here - if so I dont understand ---
**Author:** ![d.silwon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d.silwon/32/65853_2.png) [@d.silwon](https://discuss.elastic.co/u/d.silwon)\ **Post date:** [August 5, 2020, 11:42am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/10 "2020-08-05T11:42:10Z")
I suppose that your /tmp is noexec mode. Check it like this: cat /etc/fstab |grep tmp results on my michine is: /dev/mapper/rhel-tmp /tmp xfs defaults,nodev, **noexec** ,nosuid 0 0 If there is noexec then you should create some other tmp directory for elasticsearch service. For exmaple: mkdir -p /home/elasticsearch/tmp chown -R elasticsearch.elasticsearch /home/elasticsearch/ and change configuration: ```auto vi /etc/elasticsearch/jvm.options ## JVM temporary directory # -Djava.io.tmpdir=${ES_TMPDIR} -Djava.io.tmpdir=/home/elasticsearch/tmp ``` ---
**Author:** ![ian-hosting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ian-hosting/32/73300_2.png) [@ian-hosting](https://discuss.elastic.co/u/ian-hosting)\ **Post date:** [August 5, 2020, 12:39pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/11 "2020-08-05T12:39:28Z")
> [@d.silwon](#): > > If there is noexec then you should create some other tmp directory for elasticsearch service The result was actually ```auto # cat /etc/fstab |grep tmp /usr/tmpDSK /tmp ext3 defaults,noauto 0 0 ``` I went ahead and created a separate tmp directory as you suggested and that now works perfectly ! Many thanks to both of you for your help ! ---
**Author:** ![d.silwon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d.silwon/32/65853_2.png) [@d.silwon](https://discuss.elastic.co/u/d.silwon)\ **Post date:** [August 5, 2020, 12:41pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/12 "2020-08-05T12:41:39Z")
I had the same problem on the beginning on my journey with Elasticsearch. Your welcome 🙂 ---
**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\ **Post date:** [August 6, 2020, 5:31am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/13 "2020-08-06T05:31:52Z")
Wow, would NEVER have guessed that in a zillion years, and we used to set NOEXEC on /tmp as routine best practice - wonder how it got set on one of his servers but not another. Really need better logging or at least some kind of bootstrap check for this; insidious. BUT his defaults,noauto should not include NOEXEC. Man page says: rw, suid, dev, exec, auto, nouser, and async So I wonder if there is another issue that just using a different directory fixed. Also I thought CentOS 7 was already ext4; no, it's xfs - so wondering how this /tmp was created as ext3 - this suggests an unusual setup / config process. ---
**Author:** ![d.silwon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d.silwon/32/65853_2.png) [@d.silwon](https://discuss.elastic.co/u/d.silwon)\ **Post date:** [August 6, 2020, 6:27am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/14 "2020-08-06T06:27:37Z")
@Steve_Mushero We discovered this problem during installation ELK on RHEL7.8 with xfs. During installation we had the same problem with services elasticsearch and logstash. You are right that there should be more information in the log. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 3, 2020, 6:27am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-install-on-centos-7/243733/15 "2020-09-03T06:27:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.