# Kibana running issue **URL:** \ **Category:** Kibana\ **Created:** [June 5, 2017, 6:11pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312 "2017-06-05T18:11:30Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 5, 2017, 6:11pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/1 "2017-06-05T18:11:31Z")
Hello All, I installed elasticsearch 5-2-2 and kibana 5-2-2 on a single ec2 instance. I can run my elasticsearch without any issue. But when I tried to run kibana, it gives the following error. In my kibana.yml, I did the change is: server.host: "172.31.19.198" elasticsearch.url: "[http://172.31.19.198:9200](http://172.31.19.198:9200)" I don't know why it gives the error "cannot find the index". Please help me, thanks. log [16:45:57.110] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready log [16:45:57.228] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:45:57.331] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready log [16:46:00.135] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready log [16:46:00.141] [info][listening] Server running at [http://172.31.19.198:5601](http://172.31.19.198:5601) log [16:46:00.142] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow log [16:46:05.363] [info][status][plugin:elasticsearch@5.2.2] Status changed from yellow to yellow - No existing Kibana index found log [16:46:35.371] [error][status][plugin:elasticsearch@5.2.2] Status changed from yellow to red - Unable to create Kibana index ".kibana" log [16:46:35.372] [error][status][ui settings] Status changed from yellow to red - Elasticsearch plugin is red log [16:46:38.058] [error][status][plugin:elasticsearch@5.2.2] Status changed from red to red - [search\_phase\_execution\_exception] all shards failed ---
**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\ **Post date:** [June 5, 2017, 8:18pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/2 "2017-06-05T20:18:55Z")
hi @Ximeng_Zhao, That elasticsearch IP might be the public IP, and not be reachable from inside the network you're box is deployed. It seems you are running them on the same box. Try commenting out the `elasticsearch.url`. Kibana will connect over localhost. ---
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 5, 2017, 8:28pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/3 "2017-06-05T20:28:20Z")
Hi thomasneirynck, All IP I used here is private IP. Yes, I run both ES and Kibana on the same box. But I have a concern here. If I comment out elasticsearch.url , I understrand it will connect to localhost:5601. But localhost is something like 127:0:0:1. But my ec2 private IP is different from this localhost IP, how can they (ES+Kibana ) connect? Thanks ---
**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\ **Post date:** [June 5, 2017, 8:31pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/4 "2017-06-05T20:31:04Z")
Most OSs use localhost as the default loopback address. So you're request won't even go out to the network. Kibana will connect to the service running on port 9200 on that machine. ---
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 5, 2017, 8:40pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/5 "2017-06-05T20:40:43Z")
@thomasneirynck I comment out that elasticsearch.url and run the Kibana after running well on elasticsearch. Got this error: log [20:40:40.449] [info][listening] Server running at [http://172.31.19.198](http://172.31.19.198): 5601 log [20:40:40.450] [error][status][ui settings] Status changed from uninitia lized to red - Elasticsearch plugin is red log [20:40:42.767] [warning][admin][elasticsearch] Unable to revive connecti on: [http://localhost:9200/](http://localhost:9200/) log [20:40:42.769] [warning][admin][elasticsearch] No living connections log [20:40:45.272] [warning][admin][elasticsearch] Unable to revive connecti on: [http://localhost:9200/](http://localhost:9200/) ---
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 6, 2017, 7:37pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/6 "2017-06-06T19:37:36Z")
@thomasneirynck Today, I run the kibana with the following error. Do you know what's the probable problem? I changed the kibana server port to 2224. Thanks. log [19:38:15.406] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready log [19:38:15.506] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [19:38:15.536] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready log [19:38:16.440] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready log [19:38:16.451] [info][listening] Server running at [http://172.31.19.198:2224](http://172.31.19.198:2224) log [19:38:16.452] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow log [19:38:16.593] [error][status][plugin:elasticsearch@5.2.2] Status changed from yellow to red - [search\_phase\_execution\_exception] all shards failed log [19:38:16.593] [error][status][ui settings] Status changed from yellow to red - Elasticsearch plugin is red ---
**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\ **Post date:** [June 7, 2017, 3:10am UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/7 "2017-06-07T03:10:13Z")
hmm. I'm not sure what's going on. What's your ES coinfiguration? Are you sure Elasticsearch is responding to request on localhost:9200? e.h. you can test this with curl. > curl [http://localhost:9200](http://localhost:9200) Run that command from the same box that Kibana is running (which should be the same box that ES is running). You should see a JSON response with the server version and some other metadata. ---
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 7, 2017, 3:18pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/8 "2017-06-07T15:18:37Z")
@thomasneirynck Thanks for your answer. Here's more details that may help you to understand what I am doing. ES version: 5.2.2 kibana version: 5.2.2 ec2 private ip: 172-31-19-198 ec2 environment: Centos Here's what I set in the Elasticsearch.yml network.host: 172.31.19.198 node.master: true node.data: false [cluster.name](http://cluster.name): mastertest action.auto\_create\_index: true bootstrap.system\_call\_filter: false path.logs: /mnt/volume/logs path.data: /datab discovery.zen.ping.unicast.hosts: ["172.31.19.198:9300"] Here's kibana.yml server.host: "172.31.19.198" elasticsearch.url: "[http://172.31.19.198:9200](http://172.31.19.198:9200)" Summary: (1 )Elasticsearch can run successfully because I run curl '172.31.19.198:9200/' and it shows { "name" : "SH9p2cX", "cluster\_name" : "mastertest", "cluster\_uuid" : "RylkdlHvTcqfi4bWCp3ETA", "version" : { "number" : "5.2.2", "build\_hash" : "f9d9b74", "build\_date" : "2017-02-24T17:26:45.835Z", "build\_snapshot" : false, "lucene\_version" : "6.4.1" }, "tagline" : "You Know, for Search" } (2) But when start to run kibana, it gives me this error. [ximeng@ip-172-31-19-198 bin]$ ./kibana log [15:17:47.545] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready log [15:17:47.638] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [15:17:47.714] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready log [15:17:48.537] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready log [15:17:48.566] [info][listening] Server running at [http://172.31.19.198:5601](http://172.31.19.198:5601) log [15:17:48.567] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow log [15:17:48.568] [error][status][plugin:elasticsearch@5.2.2] Status changed from yellow to red - Elasticsearch is still initializing the kibana index. log [15:17:48.569] [error][status][ui settings] Status changed from yellow to red - Elasticsearch plugin is red Please let me know if you have any ideas or need more details, thanks. ---
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 7, 2017, 3:37pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/9 "2017-06-07T15:37:05Z")
Just want to follow up the above report. I used curl -XDELETE [http://192.31.19.198:9200/.kibana](http://192.31.19.198:9200/.kibana) to solve the above kibana error, but then when I start to run kibana, I got this: [ximeng@ip-172-31-19-198 bin]$ ./kibana log [15:38:13.363] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready log [15:38:13.437] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [15:38:13.493] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready log [15:38:13.675] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready log [15:38:13.681] [info][listening] Server running at [http://172.31.19.198:5601](http://172.31.19.198:5601) log [15:38:13.682] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow log [15:38:18.498] [info][status][plugin:elasticsearch@5.2.2] Status changed from yellow to yellow - No existing Kibana index found log [15:38:48.509] [error][status][plugin:elasticsearch@5.2.2] Status changed from yellow to red - Unable to create Kibana index ".kibana" log [15:38:48.509] [error][status][ui settings] Status changed from yellow to red - Elasticsearch plugin is red log [15:39:00.868] [error][status][plugin:elasticsearch@5.2.2] Status changed from red to red - [search\_phase\_execution\_exception] all shards failed Please let me know if you have any ideas, thank you. ---
**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:** [June 7, 2017, 3:41pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/10 "2017-06-07T15:41:08Z")
> [@Ximeng\_Zhao](#): > > node.data: false If you only have a single node in the cluster it must be able to hold data, otherwise Kibana will not be able to create the index it uses and there will be no data to visualise. ---
**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\ **Post date:** [June 7, 2017, 3:52pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/11 "2017-06-07T15:52:52Z")
@Christian_Dahlqvist Thanks for your answer. After I change node.data:false =\> node.date: true it works :))) Thanks so much. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 3:52pm UTC](https://discuss.elastic.co/t/kibana-running-issue/88312/12 "2017-07-05T15:52:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.