Kibana running issue

Elastic Stack Kibana
1

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"

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

2

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.

3

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

4

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.

5

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

6

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

7

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

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.

8

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

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

9

Just want to follow up the above report.

I used curl -XDELETE 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
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.

10

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.

11

@Christian_Dahlqvist
Thanks for your answer. After I change
node.data:false => node.date: true
it works :)))

Thanks so much.

12

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.