# Kibana not allowing to set up indexes **URL:** \ **Category:** Kibana\ **Created:** [March 3, 2017, 10:27pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368 "2017-03-03T22:27:42Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Ben\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/b/71e660/32.png) [@Ben\_Hoffman](https://discuss.elastic.co/u/Ben_Hoffman)\ **Post date:** [March 3, 2017, 10:27pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/1 "2017-03-03T22:27:42Z")
So Kibana gets up and running, but as soon as I type in an index to use, it crashes. The indexes do show up in Elasticsearch, and i can even query then in Kibana before I type in my index. Kibana starts like normal... ![](https://us1.discourse-cdn.com/elastic/original/3X/3/f/3f2bc047b5120ecf2a3c1de64c479eb743233f04.PNG) I Can even query data: ![](https://us1.discourse-cdn.com/elastic/original/3X/1/0/10735c7d41bfd9ded05ae11a11bd976f734a0ced.PNG) I type in the index to use.... ![](https://us1.discourse-cdn.com/elastic/original/3X/5/1/519aeaaa4fd55acd4c8d47549e7bb2439b77d293.PNG) It asks if I want to overwrite this even if it is a fresh install! ![](https://us1.discourse-cdn.com/elastic/original/3X/8/6/866354cdf1a630272bd8c7c2460fe310096276f2.PNG) None of the pages load, and the file names in the URL do not match up with what is really happening. ![](https://us1.discourse-cdn.com/elastic/original/3X/9/6/96462088d5004cba22baa8453c35b17c6a590b62.PNG) As you can see from the images above, after I type in an index kibana becomes totally unresponsive. I have tried the following already: - Remove the Kibana index from Elasticsearch - Uninstall and reinstall Kibana Both change nothing. Anyone have an idea on what to do? ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [March 5, 2017, 4:01pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/2 "2017-03-05T16:01:28Z")
Can you show what's in the Kibana log? If it's crashing that log would be very useful. Is Elasticsearch running on the same localhost as Kibana? After deleting the .kibana index, wait a few seconds for Kibana to realize it's not there and it will re-create it. Then it should only have a small config doc. But you could check that there's no index patterns defined in it with this; ```auto GET .kibana/index-pattern/_search { "query": { "match_all": {} } } ``` You could check the number of docs in the packetbeat-\* index in the dev console with; ```auto GET /_cat/indices?v ``` You could also open the browser dev console and go to the Network tab when you create the index pattern to see what happens there. Thanks, Lee ---
**Author:** ![Ben\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/b/71e660/32.png) [@Ben\_Hoffman](https://discuss.elastic.co/u/Ben_Hoffman)\ **Post date:** [March 6, 2017, 2:45pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/3 "2017-03-06T14:45:58Z")
Yes elasticsearch is running on the same host. Here is what I get from the following curl query: ``` curl -X GET 'http://localhost:9200/.kibana/index-pattern/_search' -d ' { "query": { "match_all": {} } }' ``` Results in : `{"took":1,"timed_out":false,"_shards":{"total":1,"successful":1,"failed":0},"hits":{"total":0,"max_score":null,"hits":[]}}` This query; ``` curl -X GET 'http://localhost:9200/_cat/indices?v' ``` Results in: ``` health status index uuid pri rep docs.count docs.deleted store.size pri.store.size yellow open filebeat-2017.03.02 NAr1w4LCQdKLISVscZulnA 5 1 5632435 0 3.7gb 3.7gb yellow open filebeat-2017.03.01 axXtX1Z3QeGc7LwWOZ1HRQ 5 1 464 0 728.3kb 728.3kb yellow open packetbeat-2017.03.02 1K8C3KALQKCOMmgW-K_7FA 5 1 6667705 0 2gb 2gb yellow open packetbeat-2017.03.03 KPzK8N6TROGNpeVzL_ELMQ 5 1 1780403 0 551.8mb 551.8mb yellow open packetbeat-2017.03.01 8BJxXkjGSOeiZXq_LCai8w 5 1 3396 0 1.4mb 1.4mb yellow open filebeat-2017.03.03 WvA_F5dIQx-QguXDsx4Y4g 5 1 2779781 0 1.8gb 1.8gb yellow open .kibana ZQLV17IWReqgfTxfB-4UzQ 1 1 1 0 3.1kb 3.1kb ``` Kibana is running as a service on CentOS, so the logs were not saved due to them being sent to stdout. I just changed to it a log file though, so I will have those soon ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [March 6, 2017, 7:32pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/4 "2017-03-06T19:32:20Z")
If you don't see logs in `/var/log/kibana/` and your CentOS is running systemd, you might find the logs with; `journalctl -u kibana.service` ---
**Author:** ![Ben\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/b/71e660/32.png) [@Ben\_Hoffman](https://discuss.elastic.co/u/Ben_Hoffman)\ **Post date:** [March 6, 2017, 9:33pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/5 "2017-03-06T21:33:35Z")
Logs are here on [pastebin](http://pastebin.com/U9k0xzVY) ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [March 7, 2017, 4:38pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/6 "2017-03-07T16:38:04Z")
In your logs; `Error: EACCES: permission denied, open '/var/log/kibana.log'` Can you fix that and post some new logs please? Thanks, Lee ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 4, 2017, 4:38pm UTC](https://discuss.elastic.co/t/kibana-not-allowing-to-set-up-indexes/77368/7 "2017-04-04T16:38:23Z")
Closed on April 4, 2017, 4:38pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.