# \[Solved\] Cannot start ES 7.0.1 on Fedora 30 unless "xpack.ml.enabled: false" is set **URL:** \ **Category:** Elasticsearch\ **Created:** [May 6, 2019, 2:32am UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693 "2019-05-06T02:32:30Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Damian\_Jimenez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/damian_jimenez/32/45579_2.png) [@Damian\_Jimenez](https://discuss.elastic.co/u/Damian_Jimenez)\ **Post date:** [May 6, 2019, 2:32am UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/1 "2019-05-06T02:32:30Z")
**Solution:** The solution was to install libxcrypt-compat (`sudo dnf install libxcrypt-compat`) as pointed out in the thread below. After installing that no further custom configuration was necessary and the service started without needing to set `xpack.ml.enabled: false` (i.e., default out-of-the-box config worked). Original Issue is below. Just wondering if there are known issues with running ES 7.0.1 on Fedora 30? I was unable to start it until I set the `xpack.ml.enabled: false` in `/etc/elasticsearch/elasticsearch.yml`. Pretty much running the default settings aside from that. I installed it via the RPM package and am starting it with systemd. The journalctl output is below: ```auto May 05 20:58:24 fedora-server elasticsearch[12275]: [2019-05-05T20:58:24,257][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [fedora-server] uncaught exception in thread [main] May 05 20:58:24 fedora-server elasticsearch[12275]: org.elasticsearch.bootstrap.StartupException: ElasticsearchException[Failed to create native process factories for Machine Learning]; nested: FileNotFoundException[/tmp/elasticsearch-16369124385724695169/controller_log_12275 (No such fi> May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:163) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: Caused by: org.elasticsearch.ElasticsearchException: Failed to create native process factories for Machine Learning May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.xpack.ml.MachineLearning.createComponents(MachineLearning.java:433) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.node.Node.lambda$new$9(Node.java:438) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1654) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578) ~[?:?] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.node.Node.(Node.java:441) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.node.Node.(Node.java:251) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:211) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:211) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:325) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-7.0.1.jar:7.0.1] May 05 20:58:24 fedora-server elasticsearch[12275]: ... 6 more May 05 20:58:24 fedora-server elasticsearch[12275]: ... 6 more May 05 20:58:24 fedora-server systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE May 05 20:58:24 fedora-server systemd[1]: elasticsearch.service: Failed with result 'exit-code'. ``` ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [May 6, 2019, 8:18am UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/2 "2019-05-06T08:18:44Z")
Is it possible, that you are not allowed to write into the `/tmp` filesystem with the user that is starting Elasticsearch? ---
**Author:** ![Damian\_Jimenez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/damian_jimenez/32/45579_2.png) [@Damian\_Jimenez](https://discuss.elastic.co/u/Damian_Jimenez)\ **Post date:** [May 6, 2019, 9:43am UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/3 "2019-05-06T09:43:19Z")
I actually thought that at first, but I tried specifying a custom tmp directory via `ES_TMPDIR=/elasticsearch_tmp` and `ES_JAVA_OPTS="-Djna.tmpdir=/elasticsearch_tmp"` in `/etc/sysconfig/elasticsearch` and gave the `elasticsearch` user and group ownership of it and did `chmod 777` to the directory just to make sure there was not doubt it didn't have access. With this it still results in: ```auto org.elasticsearch.bootstrap.StartupException: ElasticsearchException[Failed to create native process factories for Machine Learning]; nested: FileNotFoundException[/elasticsearch_tmp/controller_log_4828 (No such file or directory)]; ``` I also see a folder `jna--1985354563` in that directory I created, so it is able to access it and create files/folders inside it. After that I reverted the changes to the tmp dir and proceeded to set `xpack.ml.enabled: false` to get it to work for now while I try and get this sorted. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [May 6, 2019, 11:32am UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/4 "2019-05-06T11:32:51Z")
you can try to create `/elasticsearch_tmp/elasticsearch` and give that directory all the permissions - this is IIRC where ML needs to have write permissions. If that does not work either, please go ahead and open an issue in the [Elasticsearch repo](https://github.com/elastic/elasticsearch/issues/new) ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [May 6, 2019, 9:36pm UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/5 "2019-05-06T21:36:30Z")
This is likely [elastic/ml-cpp#478](https://github.com/elastic/ml-cpp/issues/478). Please try installing the package `libxcrypt-compat` and let us know if the issue otherwise persists. ---
**Author:** ![Hoggins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hoggins/32/7891_2.png) [@Hoggins](https://discuss.elastic.co/u/Hoggins)\ **Post date:** [June 3, 2019, 1:34pm UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/6 "2019-06-03T13:34:03Z")
That's exactly what happened on my 6.8.0 with my brand new Fedora 30 install, installing `libxcrypt-compat` did the trick! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 1, 2019, 1:34pm UTC](https://discuss.elastic.co/t/solved-cannot-start-es-7-0-1-on-fedora-30-unless-xpack-ml-enabled-false-is-set/179693/7 "2019-07-01T13:34:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.