# New install of Kibana can't get data from Elasticsearch, or? **URL:** \ **Category:** Kibana\ **Created:** [March 16, 2016, 7:05pm UTC](https://discuss.elastic.co/t/new-install-of-kibana-cant-get-data-from-elasticsearch-or/44602 "2016-03-16T19:05:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\ **Post date:** [March 16, 2016, 7:05pm UTC](https://discuss.elastic.co/t/new-install-of-kibana-cant-get-data-from-elasticsearch-or/44602/1 "2016-03-16T19:05:17Z")
This has to be something simple, but after burning more than a day over this, I thought I'd ask. This is a new install on Elasticsearch and Kibana. I'll get to Logstash later, unless its needed now. It appears Elasticsearch is alive and well: C:\elasticsearch\bin\>elasticsearch [2016-03-17 10:00:28,934][INFO][node] [Runner] version[2.2.0], pid[6548], build[8ff36d1/2016-01-27T13:32:39Z] [2016-03-17 10:00:28,934][INFO][node] [Runner] initializing ... [2016-03-17 10:00:29,372][INFO][plugins] [Runner] modules [lang-expression, lang-groovy], plugins , sites [2016-03-17 10:00:29,387][INFO][env] [Runner] using [1] data paths, mounts [[(C:)]], net usable\_space [461.4gb], net total\_space [904.1gb], spins? [unknown], types [NTFS] [2016-03-17 10:00:29,387][INFO][env] [Runner] heap size [910.5mb], compressed ordinary object pointers [true] [2016-03-17 10:00:31,053][INFO][node] [Runner] initialized [2016-03-17 10:00:31,053][INFO][node] [Runner] starting ... [2016-03-17 10:00:31,303][INFO][transport] [Runner] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300}, {[::1]:9300} [2016-03-17 10:00:31,318][INFO][discovery] [Runner] elasticsearch/6ymG29BjSmewI-TCj3Jmuw [2016-03-17 10:00:35,354][INFO][cluster.service] [Runner] new\_master {Runner}{6ymG29BjSmewI-TCj3Jmuw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected\_as\_master, [0] joins received) [2016-03-17 10:00:35,416][INFO][gateway] [Runner] recovered [0] indices into cluster\_state [2016-03-17 10:00:35,526][INFO][http] [Runner] publish\_address {127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200}, {[::1]:9200} [2016-03-17 10:00:35,526][INFO][node] [Runner] started epoch timestamp cluster status node.total node.data shards pri relo init unassign pending\_tasks max\_task\_wait\_time active\_shards\_percent 1458235976 10:32:56 elasticsearch green 1 1 0 0 0 0 0 0 - 100.0% All commands to Elasticsearch seem to work as expected, and browsing to [http://localhost:9200](http://localhost:9200) returns a json record as expected. Starting Kibana seems to go OK: C:\kibana\>bin\kibana log [10:36:12.666] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready log [10:36:12.697] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [10:36:12.713] [info][status][plugin:kbn\_vislib\_vis\_types] Status changed from uninitialized to green - Ready log [10:36:12.728] [info][status][plugin:markdown\_vis] Status changed from uninitialized to green - Ready log [10:36:12.728] [info][status][plugin:metric\_vis] Status changed from uninitialized to green - Ready log [10:36:12.728] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready log [10:36:12.744] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready log [10:36:12.744] [info][status][plugin:table\_vis] Status changed from uninitialized to green - Ready log [10:36:12.760] [info][listening] Server running at [http://localhost:5601](http://localhost:5601) log [10:36:17.803] [info][status][plugin:elasticsearch] Status changed from yellow to yellow - No existing Kibana index found log [10:36:20.832] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready Going to the Kibana Web U/I seems OK as well: ![](https://us1.discourse-cdn.com/elastic/original/2X/b/be5b42c79cd1a9c22446f6093ab70b770207cf91.PNG) If I just accept the default "logstash-\*" and press ENTER, I see: ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e81e16851d37eb58ea0f4f2f42f417c21a620d3c.PNG) I'm running on Windows 10 and following [https://www.elastic.co/guide/en/kibana/current/setup.html](https://www.elastic.co/guide/en/kibana/current/setup.html). Any help would be appreciated. Thanks in advance! ---
**Author:** ![Court](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/court/32/6640_2.png) [@Court](https://discuss.elastic.co/u/Court)\ **Post date:** [March 17, 2016, 6:41pm UTC](https://discuss.elastic.co/t/new-install-of-kibana-cant-get-data-from-elasticsearch-or/44602/2 "2016-03-17T18:41:19Z")
Do you actually have indexes that begin with "logstash-"? Kibana can't create index patterns that do not match any existing indexes in elasticsearch. ---
**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\ **Post date:** [March 17, 2016, 8:47pm UTC](https://discuss.elastic.co/t/new-install-of-kibana-cant-get-data-from-elasticsearch-or/44602/3 "2016-03-17T20:47:56Z")
I did have logstash data, but I think I identified the problem. First I downloaded the sample "bank" data (1000 records) and used Elasticsearch to import it. I still couldn't access anything. What finally worked was using Elasticsearch to delete the .kibana index. It must have somehow been corrupted. I was then able to use Kibana to index and access the imported "bank" data. Kibana seems to be operating normally. As a side note (or new topic?), I'm seeing a large number of java errors being thrown from Elasticsearch when doing ANYTHING from Kibana. I can capture and send if you would like... ---
**Author:** ![Court](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/court/32/6640_2.png) [@Court](https://discuss.elastic.co/u/Court)\ **Post date:** [March 17, 2016, 9:23pm UTC](https://discuss.elastic.co/t/new-install-of-kibana-cant-get-data-from-elasticsearch-or/44602/4 "2016-03-17T21:23:31Z")
I'm glad you got it sorted. I probably won't be any help with elasticsearch java errors, but I urge you to post them to the elasticsearch forum to see if you can track down a root cause: [https://discuss.elastic.co/c/elasticsearch](https://discuss.elastic.co/c/elasticsearch) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:58pm UTC](https://discuss.elastic.co/t/new-install-of-kibana-cant-get-data-from-elasticsearch-or/44602/5 "2017-07-06T13:58:44Z")