# ML Job failed: autodetect process stopped unexpectedly: Fatal error **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-machine-learning\ **Created:** [June 28, 2018, 10:07pm UTC](https://discuss.elastic.co/t/ml-job-failed-autodetect-process-stopped-unexpectedly-fatal-error/137867 "2018-06-28T22:07:15Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![dkyle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkyle/32/59114_2.png) [@dkyle](https://discuss.elastic.co/u/dkyle)\ **Post date:** [June 29, 2018, 9:12am UTC](https://discuss.elastic.co/t/ml-job-failed-autodetect-process-stopped-unexpectedly-fatal-error/137867/2 "2018-06-29T09:12:42Z")
Hi Robert, > Fatal error: 'si\_signo 4, si\_code: 2, si\_errno: 0, .. The signal is SIGILL which means the CPU didn't understand an instruction and is one of the signals that cannot be handled. Please review the linked comment for details. > [@Machine learning doesn't work but shows no error](https://discuss.elastic.co/t/machine-learning-doesnt-work-but-shows-no-error/132766/5): > > Signal 4 is SIGILL, which makes me wonder if the CPU in the machine you’re running ML on is too old to support the instruction sets we’re using. We’re using SSE4.2. There’s a list of the CPUs that support it here: [https://en.wikipedia.org/wiki/SSE4#Supporting\_CPUs](https://en.wikipedia.org/wiki/SSE4#Supporting_CPUs) Is your CPU listed as supporting SSE4.2 (or newer than the ones on the list)? If not, would you be able to add a newer machine to your cluster to use as an ML node? You could set node.ml to false on all the other nodes to ensure M… --- _[View the full topic](https://discuss.elastic.co/t/ml-job-failed-autodetect-process-stopped-unexpectedly-fatal-error/137867)._