# Unable to open Machine Learning job
**URL:** https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359
**Category:** Elasticsearch
**Tags:** elastic-stack-machine-learning
**Created:** [July 31, 2018, 12:43pm UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359 "2018-07-31T12:43:36Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Alon\_Goldstein](https://discuss.elastic.co/u/Alon_Goldstein)
#### Post date: [July 31, 2018, 12:43pm UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/1 "2018-07-31T12:43:36Z")
Hi,
I'm using Elasticsearch and Kibana version 6.2.4 with Platinum license.
Every time I create a Machine Learning job (through API or Kibana), I'm getting the following error in ES log:
[2018-07-31T08:36:30,172][WARN][r.suppressed] path: /\_xpack/ml/anomaly\_detectors/aa/\_open, params: {job\_id=aa}
org.elasticsearch.transport.RemoteTransportException: [[zlt23646.vci.att.com](http://zlt23646.vci.att.com)][135.68.47.160:9300][cluster:admin/xpack/ml/job/open]
Caused by: org.elasticsearch.ElasticsearchException: Unexpected job state [failed] while waiting for job to be opened
at org.elasticsearch.xpack.core.ml.utils.ExceptionsHelper.serverError(ExceptionsHelper.java:43) ~[?:?]
at org.elasticsearch.xpack.ml.action.TransportOpenJobAction$JobPredicate.test(TransportOpenJobAction.java:351) ~[?:?]
at org.elasticsearch.xpack.ml.action.TransportOpenJobAction$JobPredicate.test(TransportOpenJobAction.java:326) ~[?:?]
at org.elasticsearch.xpack.core.persistent.PersistentTasksService.lambda$waitForPersistentTaskStatus$4(PersistentTasksService.java:157) ~[?:?]
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.clusterChanged(ClusterStateObserver.java:186) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.cluster.service.ClusterApplierService.lambda$callClusterStateListeners$7(ClusterApplierService.java:509) ~[elasticsearch-6.2.4.jar:6.2.4]
at java.util.concurrent.ConcurrentHashMap$KeySpliterator.forEachRemaining(ConcurrentHashMap.java:3527) ~[?:1.8.0\_91]
at java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:743) ~[?:1.8.0\_91]
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) ~[?:1.8.0\_91]
at org.elasticsearch.cluster.service.ClusterApplierService.callClusterStateListeners(ClusterApplierService.java:506) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.cluster.service.ClusterApplierService.applyChanges(ClusterApplierService.java:489) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.cluster.service.ClusterApplierService.runTask(ClusterApplierService.java:432) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.cluster.service.ClusterApplierService$UpdateTask.run(ClusterApplierService.java:161) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:573) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:244) ~[elasticsearch-6.2.4.jar:6.2.4]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:207) ~[elasticsearch-6.2.4.jar:6.2.4]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0\_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0\_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_91]
What am I doing wrong?
Thanks,
Alon
---
### Author:  [@dkyle](https://discuss.elastic.co/u/dkyle)
#### Post date: [July 31, 2018, 2:02pm UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/2 "2018-07-31T14:02:59Z")
Hi Alon,
Can you tell me a little more about your set up please. Which OS are you using, have you upgraded Elasticsearch recently? Does this error occur for all jobs you create or just certain ones and can you share the job configuration ?
You have a Platinum license have you raised the issue with support?
---
### Author:  [@droberts195](https://discuss.elastic.co/u/droberts195)
#### Post date: [August 1, 2018, 6:40am UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/3 "2018-08-01T06:40:42Z")
The trick to solving this will be to look in the log file of the node where the ML job attempted to start. That will contain the underlying error message. How many ML nodes are in your cluster? By that I mean nodes with `node.ml: true` in `elasticsearch.yml` or no mention of `node.ml` (since `true` is the default). If it’s just a few maybe you could check their logs around the time of the error.
---
### Author:  [@Alon\_Goldstein](https://discuss.elastic.co/u/Alon_Goldstein)
#### Post date: [August 1, 2018, 7:39am UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/4 "2018-08-01T07:39:34Z")
I am using a two node cluster, running on Linux machines.
No upgrade with ML jobs was done.
This error occurs for every job I'm trying to create, no matter what the data or job configuration is.
I should probably mention that I changed the configuration for the elastic TMP folder, since previously the ML job error indicated it couldn't find the folder in the /tmp folder on the machine.
---
### Author:  [@Alon\_Goldstein](https://discuss.elastic.co/u/Alon_Goldstein)
#### Post date: [August 1, 2018, 7:41am UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/5 "2018-08-01T07:41:22Z")
What I shared in the original message is the exact error I'm getting in the log files.
No other underlying error messages unfortunately...
there is no mention of node.ml in elasticsearch .yml
Also, when restarting the node, the log file states that node.ml=true
---
### Author:  [@droberts195](https://discuss.elastic.co/u/droberts195)
#### Post date: [August 1, 2018, 8:07am UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/6 "2018-08-01T08:07:25Z")
So it’s a single node cluster?
---
### Author:  [@droberts195](https://discuss.elastic.co/u/droberts195)
#### Post date: [August 1, 2018, 8:16am UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/7 "2018-08-01T08:16:15Z")
Sorry I only saw your second reply.
The temp problem is this: [https://github.com/elastic/elasticsearch/issues/31732](https://github.com/elastic/elasticsearch/issues/31732)
It can cause the original error you posted. Did you change the temp directory on both nodes? If you only changed it on one node then try changing it on the second one as well and see if that solves the ML job startup problem.
The original error you posted was a remote transport exception, which means the underlying problem was on the other node. So I’m pretty sure there will be an exception in the log on that other node. But probably the exception is the missing temp directory, and you’re not connecting it with the failure to open the job. If that’s the case then explicitly setting the temp directory on both nodes will solve it.
---
### Author:  [@Alon\_Goldstein](https://discuss.elastic.co/u/Alon_Goldstein)
#### Post date: [August 1, 2018, 11:51am UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/8 "2018-08-01T11:51:25Z")
Works!!!
Thanks a lot!
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 29, 2018, 10:04pm UTC](https://discuss.elastic.co/t/unable-to-open-machine-learning-job/142359/9 "2018-10-29T22:04:20Z")