# Machine Learning: Could not create job

**URL:** <https://discuss.elastic.co/t/machine-learning-could-not-create-job/122037>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [March 1, 2018, 11:00am UTC](https://discuss.elastic.co/t/machine-learning-could-not-create-job/122037 "2018-03-01T11:00:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [March 6, 2018, 3:52am UTC](https://discuss.elastic.co/t/machine-learning-could-not-create-job/122037/4 "2018-03-06T03:52:26Z")

</div>

Communications between the elasticsearch JVM and the autodetect process (which ML runs) is done via named pipes, these pipes are created in /tmp. In the log there is a message that you posted, it mentions that a file in ES\_HOME/tmp cannot be read.

This /tmp directory must be readable, if it is mounted with no\_exec then autodetect cannot start.

/tmp is the default temporary directory the JVM uses but you can change this with the JVM option:

`-Djava.io.tmpdir=/var/data/elasticsearch/tmp`

You could try adding that setting to ES\_HOME/config/jvm.options without a suitable choice of tmpdir. This will required a restart of elasticsearch

---

_[View the full topic](https://discuss.elastic.co/t/machine-learning-could-not-create-job/122037)._
