# Plugin:elasticsearch@6.2.4 - Status changed from yellow to red **URL:** \ **Category:** Elasticsearch\ **Created:** [May 22, 2018, 5:22pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863 "2018-05-22T17:22:54Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Rubens\_Zimbres](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Rubens\_Zimbres](https://discuss.elastic.co/u/Rubens_Zimbres)\ **Post date:** [May 22, 2018, 5:22pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/1 "2018-05-22T17:22:54Z")
I created a pipeline in AWS where Elasticsearch sends JSON data from AWS IoT to Kibana. I configured the kibana.yml file as follows: server.port: 5601 server.host: "localhost" elasticsearch.url: "[https://search-domain-1234-abcdef.us-east-1.es.amazonaws.com/](https://search-domain-1234-abcdef.us-east-1.es.amazonaws.com/)" elasticsearch.requestTimeout: 30000 I am able to open Kibana in my browser on [http://localhost:5601](http://localhost:5601) but I get the following error at Kibana page: Request Timeout after 3000ms ![Kibana_error](https://us1.discourse-cdn.com/elastic/original/3X/5/9/5940e76b6704ef76f36463733ac85690fe308716.png) Also, some issues in the command line: log [17:16:27.406] [error][status][plugin:elasticsearch@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms respons [17:16:27.741] GET / 200 70ms - 9.0B ops [17:16:28.590] memory: 78.7MB uptime: 0:00:06 load: [2.04 1.48 1.25] delay: 3.994 ops [17:16:33.590] memory: 79.1MB uptime: 0:00:11 load: [2.12 1.50 1.25] delay: 1.455 ops [17:16:38.589] memory: 79.4MB uptime: 0:00:16 load: [2.19 1.53 1.26] delay: 0.598 ops [17:16:43.593] memory: 79.5MB uptime: 0:00:21 load: [2.18 1.54 1.27] delay: 0.248 ops [17:16:48.596] memory: 79.7MB uptime: 0:00:26 load: [2.24 1.56 1.28] delay: 0.502 ops [17:16:53.598] memory: 79.9MB uptime: 0:00:31 load: [2.70 1.67 1.31] delay: 0.500 respons [17:16:27.850] GET /app/kibana 503 30162ms - 9.0B respons [17:16:58.026] GET /bundles/vendors.style.css?v=16627 304 27ms - 9.0B respons [17:16:58.031] GET /bundles/status\_page.style.css?v=16627 304 27ms - 9.0B respons [17:16:58.055] GET /ui/favicons/favicon-32x32.png 304 10ms - 9.0B respons [17:16:58.029] GET /bundles/commons.style.css?v=16627 304 39ms - 9.0B respons [17:16:58.069] GET /ui/favicons/favicon-16x16.png 304 3ms - 9.0B respons [17:16:58.031] GET /bundles/vendors.bundle.js?v=16627 304 59ms - 9.0B respons [17:16:58.140] GET /bundles/commons.bundle.js?v=16627 304 5ms - 9.0B respons [17:16:58.162] GET /bundles/status\_page.bundle.js?v=16627 304 2ms - 9.0B respons [17:16:58.315] GET /api/status 200 4ms - 9.0B respons [17:16:58.335] GET /plugins/kibana/assets/discover.svg 304 1ms - 9.0B respons [17:16:58.337] GET /plugins/kibana/assets/visualize.svg 304 10ms - 9.0B respons [17:16:58.338] GET /plugins/kibana/assets/dashboard.svg 304 12ms - 9.0B respons [17:16:58.338] GET /plugins/timelion/icon.svg 304 20ms - 9.0B respons [17:16:58.344] GET /plugins/kibana/assets/wrench.svg 304 16ms - 9.0B respons [17:16:58.345] GET /plugins/kibana/assets/settings.svg 304 17ms - 9.0B respons [17:16:58.359] GET /ui/favicons/favicon-32x32.png 304 5ms - 9.0B respons [17:16:58.359] GET /plugins/kibana/assets/play-circle.svg 304 7ms - 9.0B respons [17:16:58.375] GET /ui/favicons/favicon-16x16.png 304 2ms - 9.0B I'm not using X-Pack so far. Can someone bring some light on this issue? Thanks in advance. ---
**Author:** ![eedugon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eedugon/32/45404_2.png) [@eedugon](https://discuss.elastic.co/u/eedugon)\ **Post date:** [May 22, 2018, 7:30pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/2 "2018-05-22T19:30:54Z")
Hi @Rubens_Zimbres, I might be wrong, but it looks to me that somehow your kibana instance is not able to connect with Elasticsearch. Have you tried to curl from kibana terminal towards the endpoint `https://search-domain-1234-abcdef.us-east-1.es.amazonaws.com/`? all good? Is elasticsearch answering there? You are not using x-pack but the endpoint is HTTPS. Is the https endpoint some kind of proxy or AWS load balancer? If elasticsearch is really listening in HTTPS then x-pack is being used, and in such case you would need x-pack configured in kibana also. If you have direct access between kibana and elasticsearch VMs you could also try setting the endpoint to the elasticsearch service itself, not via any kind of proxy/load balancer (http://ip\_elasticsearch:9200 probably). If nothing helps feel free to share the logs from kibana since you start the service. Regards! Eduardo ---
**Author:** ![Rubens\_Zimbres](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Rubens\_Zimbres](https://discuss.elastic.co/u/Rubens_Zimbres)\ **Post date:** [May 24, 2018, 1:17pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/3 "2018-05-24T13:17:53Z")
Hi @eedugon, thanks for the prompt response. I successfully curled from ElasticSearch endpoint: { "name" : "12345y", "cluster\_name" : "1234567:domain", "cluster\_uuid" : "abcd12345", "version" : { "number" : "6.2.2", "build\_hash" : "10b1edd", "build\_date" : "2018-02-28T15:42:08.616107Z", "build\_snapshot" : false, "lucene\_version" : "7.2.1", "minimum\_wire\_compatibility\_version" : "5.6.0", "minimum\_index\_compatibility\_version" : "5.0.0" }, "tagline" : "You Know, for Search" } However when i run bin/kibana I get: log [13:32:53.130] [info][status][plugin:kibana@6.2.4] Status changed from uninitialized to green - Ready log [13:32:53.176] [info][status][plugin:elasticsearch@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.181] [info][status][plugin:xpack\_main@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.188] [info][status][plugin:searchprofiler@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.196] [info][status][plugin:ml@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.264] [info][status][plugin:tilemap@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.268] [info][status][plugin:watcher@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.306] [info][status][plugin:license\_management@6.2.4] Status changed from uninitialized to green - Ready log [13:32:53.475] [info][status][plugin:timelion@6.2.4] Status changed from uninitialized to green - Ready log [13:32:53.478] [info][status][plugin:graph@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:53.485] [info][status][plugin:monitoring@6.2.4] Status changed from uninitialized to green - Ready log [13:32:54.265] [info][status][plugin:reporting@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:54.289] [info][status][plugin:security@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:54.290] [warning][security] Session cookies will be transmitted over insecure connections. This is not recommended. log [13:32:54.331] [info][status][plugin:grokdebugger@6.2.4] Status changed from uninitialized to green - Ready log [13:32:54.341] [info][status][plugin:dashboard\_mode@6.2.4] Status changed from uninitialized to green - Ready log [13:32:54.345] [info][status][plugin:logstash@6.2.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [13:32:54.363] [info][status][plugin:apm@6.2.4] Status changed from uninitialized to green - Ready log [13:32:54.374] [info][status][plugin:console@6.2.4] Status changed from uninitialized to green - Ready log [13:32:54.377] [info][status][plugin:metrics@6.2.4] Status changed from uninitialized to green - Ready log [13:32:54.394] [info][listening] Server running at [http://localhost:5601](http://localhost:5601) log [13:32:56.509] [error][status][plugin:xpack\_main@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.511] [error][status][plugin:searchprofiler@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.513] [error][status][plugin:ml@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.514] [error][status][plugin:tilemap@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.515] [error][status][plugin:watcher@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.516] [error][status][plugin:graph@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.518] [error][status][plugin:reporting@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.519] [error][status][plugin:security@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.521] [error][status][plugin:logstash@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:32:56.522] [error][status][plugin:elasticsearch@6.2.4] Status changed from yellow to red - Request Timeout after 3000ms log [13:33:26.531] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Error: Request Timeout after 30000ms log [13:33:26.535] [error][status][plugin:xpack\_main@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.540] [error][status][plugin:searchprofiler@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.556] [error][status][plugin:ml@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.561] [error][status][plugin:tilemap@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.565] [error][status][plugin:watcher@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.573] [error][status][plugin:graph@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.582] [error][status][plugin:reporting@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.586] [error][status][plugin:security@6.2.4] Status changed from red to red - Request Timeout after 30000ms log [13:33:26.590] [error][status][plugin:logstash@6.2.4] Status changed from red to red - Request Timeout after 30000ms So far I just altered cluster.name in elasticsearch.yml I set up passwords at kibana.yml: elasticsearch.url: "[https://search-domain12345.us-east-1.es.amazonaws.com/](https://search-domain12345.us-east-1.es.amazonaws.com/)" elasticsearch.password: secret1234 xpack.monitoring.elasticsearch.password: secret226677 And cluster.name at elasticsearch.yml Now, Kibana at localhost:5601 tells me: "Login is currently disabled. Administrators should consult the Kibana logs for more details." When I run: curl '[http://localhost:9200/?pretty](http://localhost:9200/?pretty)' I get: { "error" : { "root\_cause" : [ { "type" : "security\_exception", "reason" : "missing authentication token for REST request [/?pretty]", "header" : { "WWW-Authenticate" : "Basic realm="security" charset="UTF-8"" } } ], "type" : "security\_exception", "reason" : "missing authentication token for REST request [/?pretty]", "header" : { "WWW-Authenticate" : "Basic realm="security" charset="UTF-8"" } }, "status" : 401 } Also: curl -u kibana:changeme [http://localhost:9200/\_xpack](http://localhost:9200/_xpack) curl: (7) Failed to connect to localhost port 9200: Connection refused No firewall running on ports 5601 an 9200 ---
**Author:** ![eedugon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eedugon/32/45404_2.png) [@eedugon](https://discuss.elastic.co/u/eedugon)\ **Post date:** [May 25, 2018, 10:37am UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/4 "2018-05-25T10:37:59Z")
Hi! Please try to explain the architecture a little bit more in terms of hosts and what service is running in each host. Also share your elasticsearch.yml files from all elasticsearch nodes of the cluster. Configuring Kibana to access Elasticsearch is quite easy, but you need to know very well your elasticsearch cluster. Also take in mind that for `production mode`, SSL and X-Pack are mandatory in 6.2.x. [https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#\_development\_vs\_production\_mode](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#_development_vs_production_mode) So, as soon as you have more than 1 node in your ES cluster (or if you want to accept remote connections (from other than `localhost`)), you are going to need SSL certificates and use HTTPS. In case you need: [https://www.elastic.co/guide/en/x-pack/current/ssl-tls.html](https://www.elastic.co/guide/en/x-pack/current/ssl-tls.html) Anyway, the error reported in your output is claiming that x-pack is not installed in Elasticsearch cluster: ```auto log [13:33:26.531] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Error: Request Timeout after 30000ms ``` I would recommend to install X-pack in your ES cluster and setup the password for the main builtin users, as explained here: [https://www.elastic.co/guide/en/elasticsearch/reference/6.2/installing-xpack-es.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/installing-xpack-es.html) In short: 1. Stop Elasticsearch in all cluster nodes. 2. Install x-pack plugin in all your cluster nodes. ```auto bin/elasticsearch-plugin install x-pack ``` 1. Start Elasticsearch in all nodes. 2. Setup the basic passwords for `elastic`, `kibana` and `logstash_system` users. ```auto bin/x-pack/setup-passwords interactive ``` Then, configure kibana with the following settings: ```auto elasticsearch.username: "kibana" elasticsearch.password: "your_password" elasticsearch.url: "http://localhost:9200" ``` Note: This configuration is only valid if ES is a single-node cluster and running in the same host as kibana. If this is NOT the case, then you should configure SSL and certificates properly. Regards! Eduardo ---
**Author:** ![Rubens\_Zimbres](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Rubens\_Zimbres](https://discuss.elastic.co/u/Rubens_Zimbres)\ **Post date:** [May 25, 2018, 8:53pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/5 "2018-05-25T20:53:30Z")
@eedugon thanks for the detailed explanation. In fact I'm collecting CPU temperature from my Python notebook, sending to AWS IoT Core via MQTT using the notebook. Inside the Pyhton notebook I run Ubuntu command line 'sensors', that collects CPU temperature inside Python and sends to AWS IoT Core. After that, IoT Core has a rule that sends the JSON generated by Python to AWS Elastic Search, using Kinesis' Firehose data stream. So far, all of these features were implemented successfully. The only missing part is the Kibana connection to AWS Elasticseach. I know that I probably will have to set up a Lambda function to prepare data to Kibana, but I'm keeping simple so far. In my elasticsearch.yml I only have set up the cluster name as: cluster.name: 12345:domain Nothing else. I still have to find about the nodes. It's not in production yet, so I will be glad if I can successfully start Kibana without errors in a single node. Then I'll go to Lambda and clean data to visualize. I set up passwords for x-pack but the detail is that I didn't stop Elasticsearch to install x-pack plugin. In my kibana.yml I just set up: elasticsearch.password: abcd12345 (probably == PASSWORD elastic) xpack.monitoring.elasticsearch.password: abcd12345 (probably == PASSWORD logstash\_system) But I didn't insert "PASSWORD kibana". ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 26, 2018, 5:25am UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/6 "2018-05-26T05:25:15Z")
Based on the URL it looks like you are using AWS Elasticsearch service, is that correct? If this is the case you can disregard settings around X-Pack, as it is not available on that service. I am not sure whether it is possible to connect an external Kibana instance to a AWS Elasticsearch service cluster or not, but I would expect your cluster to come with a Kibana instance so you do not need to host your own separately. I would recommend having a look at our [Elastic Cloud](https://www.elastic.co/cloud) service as an alternative, which can also be had on AWS. ---
**Author:** ![eedugon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eedugon/32/45404_2.png) [@eedugon](https://discuss.elastic.co/u/eedugon)\ **Post date:** [May 28, 2018, 8:12am UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/7 "2018-05-28T08:12:12Z")
Hi! Yes, I fully agree with Christian. If you are using ES as a service in AWS you don't need any extra elasticsearch service running (as it won't be able to connect to the cluster at first place). About Kibana, you might be able to connect your own kibana service (without elasticsearch instance) directly to AWS (and without x-pack in such case). Although I have never tried. And as Christian suggests, take a look to [https://www.elastic.co/cloud](https://www.elastic.co/cloud) 😉 Regards! Eduardo ---
**Author:** ![Rubens\_Zimbres](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Rubens\_Zimbres](https://discuss.elastic.co/u/Rubens_Zimbres)\ **Post date:** [May 29, 2018, 3:14pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/8 "2018-05-29T15:14:16Z")
@Christian_Dahlqvist and @eedugon I solved the whole thing in a simple way. First I was trying to run Kibana from the command line to access my AWS Elasticsearch cluster. I found out that AWS Elasticsearch policy was set up to open web access and the Kibana link at the cluster page was not working. So, I updated the ES policy to a specific IP and everything worked fine. Details of the project can be found in my GitHub (See Project Part 2): > **[RubensZimbres/Repo-2018](https://github.com/RubensZimbres/Repo-2018/tree/master/CPU%2520Temperature%2520-%2520IoT%2520Project)** > > Deep Learning Summer School + Tensorflow + OpenCV cascade training + YOLO + COCO + CycleGAN + AWS EC2 Setup + AWS IoT Project + AWS SageMaker + AWS API Gateway + Raspberry Pi3 Ubuntu Core - RubensZ... ![KIBANA_WTF](https://us1.discourse-cdn.com/elastic/original/3X/d/c/dc55b1788847a890d79e1f55a20d190c3220dd59.png) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 26, 2018, 3:27pm UTC](https://discuss.elastic.co/t/plugin-elasticsearch-6-2-4-status-changed-from-yellow-to-red/132863/9 "2018-06-26T15:27:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.