# Could not start datafeed **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-machine-learning\ **Created:** [March 15, 2018, 12:39pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098 "2018-03-15T12:39:17Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Arturo](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Arturo](https://discuss.elastic.co/u/Arturo)\ **Post date:** [March 15, 2018, 12:39pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/1 "2018-03-15T12:39:17Z")
Hello, I am getting below errors while trying to create a single metric Job in machine learning tab of Kibana. Errors: Could not start datafeed for Jobname [status\_exception] cannot start datafeed [datafeed-Jobname] because job [Jobname] is not open Could not start datafeed: [status\_exception] cannot start datafeed [datafeed-Jobname] because job [Jobname] is not open The problem is that whenever a job is created, automatically is closed. I tried to open it with: POST \_xpack/ml/anomaly\_detectors/{jobname}/\_open but it returned false. I have used the sample data provided by the elastic team, in particular the stocks data. Can any one help me on this issue. ---
**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:** [March 15, 2018, 2:48pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/2 "2018-03-15T14:48:22Z")
Hi Arturo Can you tell me if an error was returned when you tired to open the job, is there anything in the elasticsearch log file you can share? Also which version of x-pack are you using and have you recently upgraded? Thanks ---
**Author:** ![Arturo](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Arturo](https://discuss.elastic.co/u/Arturo)\ **Post date:** [March 15, 2018, 3:27pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/3 "2018-03-15T15:27:13Z")
Hello David, No error was returned, only the following: ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/e/def59c2d603f81479dcd9b1ae149638c749e6d85.png) I am using the 5.4.3 version, i tried tu upgrade to last version but i was having problems with security folder after installing x-pack. ---
**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:** [March 15, 2018, 3:48pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/4 "2018-03-15T15:48:58Z")
Machine Learning was still in beta for version 5.4 there have been many improvements since 5.4 so I do really encourage you to upgrade. Perhaps I can help you with your upgrade issue did you know there is an [Upgrade Assistant](https://www.elastic.co/guide/en/kibana/5.6/xpack-upgrade-assistant.html) in 5.6? ---
**Author:** ![Arturo](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Arturo](https://discuss.elastic.co/u/Arturo)\ **Post date:** [March 16, 2018, 12:57pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/5 "2018-03-16T12:57:20Z")
Hello David, I have upgraded to version 6.2.2, I think it is the latest one. But now i can not access to kibana, the error is the following: log [12:53:06.533] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security\_exception] missing authentication token for REST request [/\_xpack], with { header={ WWW-Authenticate="Basic realm="security" charset="UTF-8"" } } :: {"path":"/\_xpack","statusCode":401,"response":"{"error":{"root\_cause":[{"type":"security\_exception","reason":"missing authentication token for REST request [/\_xpack]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}}],"type":"security\_exception","reason":"missing authentication token for REST request [/\_xpack]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}},"status":401}","wwwAuthenticateDirective":"Basic realm="security" charset="UTF-8""} The configuration of kibana.yml is the following: # Kibana is served by a back end server. This setting specifies the port to use. #server.port: 5601 # Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values. # The default is 'localhost', which usually means remote machines will not be able to connect. # To allow connections from remote users, set this parameter to a non-loopback address. #server.host: "localhost" # Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects # the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests # to Kibana. This setting cannot end in a slash. #server.basePath: "" # The maximum payload size in bytes for incoming server requests. #server.maxPayloadBytes: 1048576 # The Kibana server's name. This is used for display purposes. #server.name: "your-hostname" # The URL of the Elasticsearch instance to use for all your queries. #elasticsearch.url: "[http://localhost:9200](http://localhost:9200)" # When this setting's value is true Kibana uses the hostname specified in the server.host # setting. When the value of this setting is false, Kibana uses the hostname of the host # that connects to this Kibana instance. #elasticsearch.preserveHost: true # Kibana uses an index in Elasticsearch to store saved searches, visualizations and # dashboards. Kibana creates a new index if the index doesn't already exist. #kibana.index: ".kibana" # The default application to load. #kibana.defaultAppId: "home" # If your Elasticsearch is protected with basic authentication, these settings provide # the username and password that the Kibana server uses to perform maintenance on the Kibana # index at startup. Your Kibana users still need to authenticate with Elasticsearch, which # is proxied through the Kibana server. #elasticsearch.username: "user" #elasticsearch.password: "pass" # Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively. # These settings enable SSL for outgoing requests from the Kibana server to the browser. #server.ssl.enabled: false #server.ssl.certificate: /path/to/your/server.crt #server.ssl.key: /path/to/your/server.key # Optional settings that provide the paths to the PEM-format SSL certificate and key files. # These files validate that your Elasticsearch backend uses the same key files. #elasticsearch.ssl.certificate: /path/to/your/client.crt #elasticsearch.ssl.key: /path/to/your/client.key # Optional setting that enables you to specify a path to the PEM file for the certificate # authority for your Elasticsearch instance. #elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"] # To disregard the validity of SSL certificates, change this setting's value to 'none'. #elasticsearch.ssl.verificationMode: full # Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of # the elasticsearch.requestTimeout setting. #elasticsearch.pingTimeout: 1500 # Time in milliseconds to wait for responses from the back end or Elasticsearch. This value # must be a positive integer. #elasticsearch.requestTimeout: 30000 # List of Kibana client-side headers to send to Elasticsearch. To send _no_ client-side # headers, set this value to [] (an empty list). #elasticsearch.requestHeadersWhitelist: [authorization] # Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten # by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration. #elasticsearch.customHeaders: {} # Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable. #elasticsearch.shardTimeout: 0 # Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying. #elasticsearch.startupTimeout: 5000 # Specifies the path where Kibana creates the process ID file. #pid.file: /var/run/kibana.pid # Enables you specify a file where Kibana stores log output. #logging.dest: stdout # Set the value of this setting to true to suppress all logging output. #logging.silent: false # Set the value of this setting to true to suppress all logging output other than error messages. #logging.quiet: false # Set the value of this setting to true to log all events, including system usage information # and all requests. #logging.verbose: false # Set the interval in milliseconds to sample system and process performance # metrics. Minimum is 100ms. Defaults to 5000. #ops.interval: 5000 # The default locale. This locale can be used in certain circumstances to substitute any missing # translations. #i18n.defaultLocale: "en" How can i solve this? Thank you very much. Arturo. ---
**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:** [March 16, 2018, 1:31pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/6 "2018-03-16T13:31:36Z")
6.2 requires an additional security setup compared to 5.4 in particular you will need the kibana user's authentication settings in kibana.yml ``` elasticsearch.username: "kibana" elasticsearch.password: "kibanapassword" ``` where the password is created by the `setup-passwords` command. The guides to installing [x-pack in elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/installing-xpack-es.html) and [x-pack for kibana](https://www.elastic.co/guide/en/kibana/6.2/installing-xpack-kb.html) will take you through everything you need to do in a step-by-step manner. ---
**Author:** ![Arturo](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Arturo](https://discuss.elastic.co/u/Arturo)\ **Post date:** [March 20, 2018, 8:54am UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/7 "2018-03-20T08:54:08Z")
Hello David, I tried to re-install it, following the instructions you gave me, but i still can not loggin in kibana because of the same error: [08:51:02.581] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security\_exception] missing authentication token for REST request [/\_xpack], with { header={ WWW-Authenticate="Basic realm="security" charset="UTF-8"" } } :: {"path":"/\_xpack","statusCode":401,"response":"{"error":{"root\_cause":[{"type":"security\_exception","reason":"missing authentication token for REST request [/\_xpack]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}}],"type":"security\_exception","reason":"missing authentication token for REST request [/\_xpack]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}},"status":401}","wwwAuthenticateDirective":"Basic realm="security" charset="UTF-8""} I changed the kibana.yml with the following, where "changeme" is the setup password for elastic, kibana and logstash elasticsearch.username: "kibana" elasticsearch.password: "changeme" Maybe the password has to comply with some security rules? Thank you very much. Arturo ---
**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:** [March 20, 2018, 11:31am UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/8 "2018-03-20T11:31:07Z")
HI, > [@Arturo](#): > > [08:51:02.581] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Which license do you have for X-Pack? The warning above suggests you are using the basic license which does not support security (or Machine Learning). Did you start with a trial license and perhaps it has expired or maybe you need to [start the trial license](https://www.elastic.co/guide/en/x-pack/current/license-management.html#generated-license) You can view the current license with ``` GET /_xpack/license ``` If you have a license you need to update it with the [license API](https://www.elastic.co/guide/en/x-pack/current/license-management.html#installing-license) ---
**Author:** ![Arturo](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Arturo](https://discuss.elastic.co/u/Arturo)\ **Post date:** [March 20, 2018, 1:23pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/9 "2018-03-20T13:23:53Z")
Hi David, I write you the details of my current license, in order to know if with this one i can use the x-pack or not: "cluster\_name": "elasticsearch", "version": "6.2.2", "license": { "status": "active", "uid": "b54b91ea-b238-4b54-843f-6dc71d68e8b2", "type": "trial", "issue\_date": "2018-03-20T08:27:23.678Z", "issue\_date\_in\_millis": 1521534443678, "expiry\_date": "2018-04-19T08:27:23.678Z", "expiry\_date\_in\_millis": 1524126443678, "max\_nodes": 1000, "issued\_to": "elasticsearch", "issuer": "elasticsearch", "start\_date\_in\_millis": -1, "hkey": "d5ae4ac9a765040705068bc26bffaa1784e3e3dacba7488f0b78e7a9e6e0b706", "cluster\_needs\_tls": true }, Thank you very much ---
**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:** [March 20, 2018, 2:42pm UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/10 "2018-03-20T14:42:56Z")
You appear to have a valid trial license I'm not sure why you see this problem. @ikakavas do you have any idea what is causing this error? > [@Arturo](#): > > [08:51:02.581] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security\_exception] missing authentication token for REST request [/\_xpack], with { header={ WWW-Authenticate="Basic realm="security" charset="UTF-8"" } } :: {"path":"/\_xpack","statusCode":401,"response":"{"error":{"root\_cause":[{"type":"security\_exception","reason":"missing authentication token for REST request [/\_xpack]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}}],"type":"security\_exception","reason":"missing authentication token for REST request [/\_xpack]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}},"status":401}","wwwAuthenticateDirective":"Basic realm="security" charset="UTF-8""} ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [March 23, 2018, 10:23am UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/11 "2018-03-23T10:23:18Z")
@Arturo Can you please verify that the password you are using in kibana.yml is correct ? You can test this with `curl -XGET -u kibana 'http://localhost:9200/'` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 20, 2018, 10:23am UTC](https://discuss.elastic.co/t/could-not-start-datafeed/124098/12 "2018-04-20T10:23:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.