(Docker) Kibana displaying Kibana did not load properly. Check the server output for more information


(Brandon Mcgrath) #1

Hi!
This morning I installed Elasticsearch and Kibana 5 and it worked first time. After it was up for a few minutes i got the error message:

Kibana did not load properly. Check the server output for more information.

The images I used are: itzg/elasticsearch and the official kibana, both latest.

My docker logs aren't too useful (from what I can see). I do have some beats pointing to it which I haven't tried turning off as of yet. But here is all the information:

root@docker:~/scripts5# docker logs 4c95debe3e7bc00de97ee27df33de86f2b4b652e0bd55263dd9a1f0c155bd85a
{"type":"log","@timestamp":"2016-11-28T15:15:41Z","tags":["status","plugin:kibana@5.0.1","info"],"pid":7,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-11-28T15:15:41Z","tags":["status","plugin:elasticsearch@5.0.1","info"],"pid":7,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-11-28T15:15:41Z","tags":["status","plugin:console@5.0.1","info"],"pid":7,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-11-28T15:15:42Z","tags":["warning"],"pid":7,"kibanaVersion":"5.0.1","nodes":[{"version":"5.0.0","http":{"publish_address":"172.17.0.4:9200"},"ip":"172.17.0.4"},{"version":"5.0.0","http":{"publish_address":"172.17.0.5:9200"},"ip":"172.17.0.5"},{"version":"5.0.0","http":{"publish_address":"172.17.0.3:9200"},"ip":"172.17.0.3"},{"version":"5.0.0","http":{"publish_address":"172.17.0.2:9200"},"ip":"172.17.0.2"}],"message":"You're running Kibana 5.0.1 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v5.0.0 @ 172.17.0.4:9200 (172.17.0.4), v5.0.0 @ 172.17.0.5:9200 (172.17.0.5), v5.0.0 @ 172.17.0.3:9200 (172.17.0.3), v5.0.0 @ 172.17.0.2:9200 (172.17.0.2)"}
{"type":"log","@timestamp":"2016-11-28T15:15:42Z","tags":["status","plugin:timelion@5.0.1","info"],"pid":7,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-11-28T15:15:42Z","tags":["listening","info"],"pid":7,"message":"Server running at http://0.0.0.0:5601"}
{"type":"log","@timestamp":"2016-11-28T15:15:42Z","tags":["status","ui settings","info"],"pid":7,"state":"yellow","message":"Status changed from uninitialized to yellow - Elasticsearch plugin is yellow","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-11-28T15:15:47Z","tags":["status","plugin:elasticsearch@5.0.1","info"],"pid":7,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2016-11-28T15:15:47Z","tags":["status","plugin:elasticsearch@5.0.1","info"],"pid":7,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
{"type":"log","@timestamp":"2016-11-28T15:15:47Z","tags":["status","ui settings","info"],"pid":7,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Elasticsearch plugin is yellow"}
root@docker:~/scripts5#

The way I installed Kibana:

docker pull kibana

docker run --name kibana --link elasticsearch -p 5601:5601 -d kibana

The way I installed Elasticsearch:

docker pull itzg/elasticsearch

sysctl -w vm.max_map_count=262144

docker run -d --name elasticsearch -p 9200:9200 itzg/elasticsearch

Extra nodes:

docker run -d --name elasticsearch1 --link elasticsearch -e "UNICAST_HOSTS=elasticsearch" -e "http.host=0.0.0.0" -e "transport.host=127.0.0.1" itzg/elasticsearch

EDIT:
The log says there is no kibana index, but there is:

green open winlogbeat-2016.11.28 f8NMDnHlTCyfyLtCXM6U-A 5 1   113 0  1.1mb 572.2kb
green open topbeat-2016.11.28    ws_oMuUMTFS9Zhxp72z74A 5 1 14467 0 11.5mb   5.7mb
green open .kibana               x805S5MXQme9rEdqPLup0w 1 1     1 0  6.4kb   3.2kb

(Thomas Neirynck) #2

Could it be that Kibana is pointing at the wrong node? If you turn off those extra nodes, does the same problem persist?


(Brandon Mcgrath) #3

Its set to point to the container called "elasticsearch" which it does, and yes I have tried it with just that and it persists :\


(system) #4

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