# Kibana not started

**URL:** <https://discuss.elastic.co/t/kibana-not-started/237908>\
**Category:** Kibana\
**Created:** [June 20, 2020, 9:43am UTC](https://discuss.elastic.co/t/kibana-not-started/237908 "2020-06-20T09:43:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ronics](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@ronics](https://discuss.elastic.co/u/ronics)\
**Post date:** [June 20, 2020, 9:43am UTC](https://discuss.elastic.co/t/kibana-not-started/237908/1 "2020-06-20T09:43:12Z")

</div>

I recently upgraded elk from 7.7.0 to 7.8.0  
The elasticsearch is working fine but when I try to start kibana it shows following error. Please help  
FATAL Error: [config validation of [xpack.reporting].enabled]: definition for this key is missing

I try to check the status of kibana and found following status  
[root@localhost covid]# systemctl status kibana  
â— kibana.service - Kibana  
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)  
Active: active (running) since Sat 2020-06-20 15:30:56 +0545; 5s ago  
Main PID: 111790 (node)  
Tasks: 11  
CGroup: /system.slice/kibana.service  
â””â”€111790 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli

Jun 20 15:30:56 localhost.localdomain systemd[1]: Started Kibana.  
Jun 20 15:31:00 localhost.localdomain kibana[111790]: {"type":"log","@timestamp":"2020-06-20T09:46:00Z","tags":["warn...ss"}  
Jun 20 15:31:00 localhost.localdomain kibana[111790]: {"type":"log","@timestamp":"2020-06-20T09:46:00Z","tags":["warn...ui"}  
Hint: Some lines were ellipsized, use -l to show in full.  
[root@localhost covid]# systemctl status kibana  
â— kibana.service - Kibana  
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)  
Active: active (running) since Sat 2020-06-20 15:30:56 +0545; 10s ago  
Main PID: 111790 (node)  
Tasks: 11  
CGroup: /system.slice/kibana.service  
â””â”€111790 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli

Jun 20 15:30:56 localhost.localdomain systemd[1]: Started Kibana.  
Jun 20 15:31:00 localhost.localdomain kibana[111790]: {"type":"log","@timestamp":"2020-06-20T09:46:00Z","tags":["warn...ss"}  
Jun 20 15:31:00 localhost.localdomain kibana[111790]: {"type":"log","@timestamp":"2020-06-20T09:46:00Z","tags":["warn...ui"}  
Jun 20 15:31:06 localhost.localdomain kibana[111790]: {"type":"log","@timestamp":"2020-06-20T09:46:06Z","tags":["fata...ype.  
Jun 20 15:31:06 localhost.localdomain kibana[111790]: FATAL Error: [config validation of [xpack.reporting].enabled]:...sing  
Hint: Some lines were ellipsized, use -l to show in full.  
[root@localhost covid]#

---

<div class="post-metadata">

**Author:** ![sastorsl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sastorsl/32/44972_2.png) [@sastorsl](https://discuss.elastic.co/u/sastorsl)\
**Post date:** [June 22, 2020, 9:48am UTC](https://discuss.elastic.co/t/kibana-not-started/237908/2 "2020-06-22T09:48:29Z")

</div>

We are seeing the same issue. Installed via docker containers.

We had the following config in our kibana config file:

```
xpack.reporting.enabled: true

```

Commenting out / removing this and restarting Kibana got the instance running again.

This might be a documentation issue in 7.8 perhaps?

> <https://github.com/elastic/kibana/issues/69621>
>
> Kibana version: 7.8.0
> Elasticsearch version: 7.8.0
> Server OS version: Archlinux
> Original install method (e.g. download page, yum, from source, etc.): Arch AUR package
> Describe the...

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [June 22, 2020, 11:37am UTC](https://discuss.elastic.co/t/kibana-not-started/237908/3 "2020-06-22T11:37:42Z")

</div>

@tsullivan @joelgriffith Has this option changed in 7.8 and there are perhaps some documentation missnig for it?

Update: There seem to be an issue for that logged already, that you can follow: [https://github.com/elastic/kibana/issues/69621](https://github.com/elastic/kibana/issues/69621)

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 22, 2020, 3:56pm UTC](https://discuss.elastic.co/t/kibana-not-started/237908/4 "2020-06-22T15:56:37Z")

</div>

I commented on the issue that this was an overlooked bug that came about from Kibana Platform migration. Sorry about that!

---

<div class="post-metadata">

**Author:** ![ronics](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@ronics](https://discuss.elastic.co/u/ronics)\
**Post date:** [June 23, 2020, 5:15am UTC](https://discuss.elastic.co/t/kibana-not-started/237908/5 "2020-06-23T05:15:44Z")

</div>

Commenting out #xpack.reporting.enabled: false and restarting kibana resolve the issue.  
Thanks for the help

---

<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:** [July 21, 2020, 5:15am UTC](https://discuss.elastic.co/t/kibana-not-started/237908/6 "2020-07-21T05:15:49Z")

</div>

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