# Start Kibana

**URL:** <https://discuss.elastic.co/t/start-kibana/251116>\
**Category:** Kibana\
**Created:** [October 6, 2020, 11:54am UTC](https://discuss.elastic.co/t/start-kibana/251116 "2020-10-06T11:54:47Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 6, 2020, 11:54am UTC](https://discuss.elastic.co/t/start-kibana/251116/1 "2020-10-06T11:54:48Z")

</div>

Hello,  
i installed Kibana on Centos 7 but i have this error when i start it!

[kibana error|690x430](https://discuss.elastic.co/uploads/short-url/2FtkeIBMVAv1yFFCsMTFauIUTSz.jpeg)

how can i understand what it depends on?

Thank you

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [October 6, 2020, 2:10pm UTC](https://discuss.elastic.co/t/start-kibana/251116/2 "2020-10-06T14:10:36Z")

</div>

Hey @acastaldi84,

Have you actually checked the Kibana logs? Do you see anything suspicious there?

Also you may need to enable verbose logging to see more details (`logging.verbose: true` in `kibana.yml`).

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 6, 2020, 2:46pm UTC](https://discuss.elastic.co/t/start-kibana/251116/3 "2020-10-06T14:46:04Z")

</div>

> [@azasypkin](#):
>
> Hey @acastaldi84,
> 
> Have you actually checked the Kibana logs? Do you see anything suspicious there?
> 
> Also you may need to enable verbose logging to see more details ( `logging.verbose: true` in `kibana.yml` ).
> 
> Best,  
> Oleg

the strange thing is that if I turn the server off and on again, kibana starts .... then after a while it doesn't work anymore if I try to connect again

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [October 6, 2020, 2:50pm UTC](https://discuss.elastic.co/t/start-kibana/251116/4 "2020-10-06T14:50:57Z")

</div>

I see, yeah, we really need verbose logs to track it down.

Is there any chance that actually Elasticsearch becomes unavailable from time to time, or the issue always immediately goes away when you restart Kibana?

---

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 7, 2020, 8:36am UTC](https://discuss.elastic.co/t/start-kibana/251116/5 "2020-10-07T08:36:09Z")

</div>

why i have nothing in the log file?

---

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 28, 2020, 9:35am UTC](https://discuss.elastic.co/t/start-kibana/251116/6 "2020-10-28T09:35:04Z")

</div>

i enabled `logging.verbose: true` in `kibana.yml` but i have nothing in the log file

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [October 28, 2020, 10:33am UTC](https://discuss.elastic.co/t/start-kibana/251116/7 "2020-10-28T10:33:34Z")

</div>

Sometimes you need to also set `logging.quiet` to `false`, but apart from that you _should_ have logs. I'd also double check the file path you set in `logging.dest`.

---

<div class="post-metadata">

**Author:** ![tmp13](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tmp13/32/78005_2.png) [@tmp13](https://discuss.elastic.co/u/tmp13)\
**Post date:** [October 28, 2020, 10:47am UTC](https://discuss.elastic.co/t/start-kibana/251116/8 "2020-10-28T10:47:01Z")

</div>

> [@acastaldi84](#):
>
> enabled `logging.verbose: true` in `kibana.yml` but i have nothing in the log file

Hi. If you install from rpm and set default log location to  
`logging.dest: /var/log/kibana.log`  
then do next step  
` touch /var/log/kibana.log`  
` chown kibana: /var/log/kibana.log`

---

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 29, 2020, 3:14pm UTC](https://discuss.elastic.co/t/start-kibana/251116/9 "2020-10-29T15:14:31Z")

</div>

> [@azasypkin](#):
>
> ometimes you need to also set `logging.quiet` to `false` , but apart from that you _should_ have logs. I'd also double check the file path you set in `logging.dest` .

logging.dest: /var/log/kibana.log  
#logging.quiet: false

---

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 30, 2020, 10:15am UTC](https://discuss.elastic.co/t/start-kibana/251116/11 "2020-10-30T10:15:50Z")

</div>

ok now i have log

when i link kibana page, browser change my URL on  
[http://192.168.65.122:5601/logout?next=%2Fapp%2Fkibana%23%2Fhome%3F\_g%3D()&msg=SESSION\_EXPIRED](http://192.168.65.122:5601/logout?next=%2Fapp%2Fkibana%23%2Fhome%3F_g%3D()&msg=SESSION_EXPIRED)

with this error  
[https://discuss.elastic.co/uploads/short-url/2FtkeIBMVAv1yFFCsMTFauIUTSz.jpeg](https://discuss.elastic.co/uploads/short-url/2FtkeIBMVAv1yFFCsMTFauIUTSz.jpeg)

and this is my log:

> **[kibana](http://www.mediafire.com/file/6yvv99tb9cddyl1/kibana.log/file)**

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [October 30, 2020, 10:38am UTC](https://discuss.elastic.co/t/start-kibana/251116/12 "2020-10-30T10:38:26Z")

</div>

I think the main issue here is ` FORBIDDEN/12/index read-only ....`, usually that means you don't have enough disk space on the machine where Elasticsearch is running (ES logs should show that as well). Take a look at this discuss post [Why am I seeing a "FORBIDDEN/12/index read-only / allow delete" response against my index?](https://discuss.elastic.co/t/why-am-i-seeing-a-forbidden-12-index-read-only-allow-delete-response-against-my-index/244344).

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![acastaldi84](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@acastaldi84](https://discuss.elastic.co/u/acastaldi84)\
**Post date:** [October 30, 2020, 10:53am UTC](https://discuss.elastic.co/t/start-kibana/251116/13 "2020-10-30T10:53:27Z")

</div>

i have this disk space:

![disk](https://us1.discourse-cdn.com/elastic/original/3X/0/3/031625c8fb99a277f6a5101658c947192d3278f1.jpeg)

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [October 30, 2020, 11:09am UTC](https://discuss.elastic.co/t/start-kibana/251116/14 "2020-10-30T11:09:50Z")

</div>

You mean the partition where `96%` of the space is used? If so, then it's **definitely** not enough. Thoroughly read the [docs referenced](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html#disk-based-shard-allocation) in the post I shared with you previously.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 27, 2020, 11:09am UTC](https://discuss.elastic.co/t/start-kibana/251116/15 "2020-11-27T11:09:52Z")

</div>

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