New install of Kibana can't get data from Elasticsearch, or?

Elastic Stack Kibana
1

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 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
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:

KibanaError4.PNG1562×763 47.4 KB

If I just accept the default "logstash-*" and press ENTER, I see:

KibanaError5.PNG1441×723 22.8 KB

I'm running on Windows 10 and following https://www.elastic.co/guide/en/kibana/current/setup.html. Any help would be appreciated. Thanks in advance!

2

Do you actually have indexes that begin with "logstash-"? Kibana can't create index patterns that do not match any existing indexes in elasticsearch.

3

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...

4

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