# Failed to Start Kibana 7.16.1

**URL:** <https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900>\
**Category:** Kibana\
**Created:** [January 10, 2022, 2:46pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900 "2022-01-10T14:46:34Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhayamishra](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@abhayamishra](https://discuss.elastic.co/u/abhayamishra)\
**Post date:** [January 10, 2022, 2:46pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/1 "2022-01-10T14:46:34Z")

</div>

After Upgrading from 7.5.2or with fresh installation of Kibana 7.16.1 - it is failed to start.  
7.5.2 version was working well.  
ROR plugin is used for authentication. This is also upgraded to **readonlyrest\_kbn\_enterprise-1.37.0\_es7.16.1**

```auto
systemctl status -l kibana
● kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Mon 2022-01-10 08:41:14 UTC; 28s ago
     Docs: https://www.elastic.co
  Process: 3336 ExecStart=/usr/share/kibana/bin/kibana --logging.dest="/var/log/kibana/kibana.log" --pid.file="/run/kibana/kibana.pid" (code=exited, status=1/FAILURE)
 Main PID: 3336 (code=exited, status=1/FAILURE)

Jan 10 08:41:11 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service: main process exited, code=exited, status=1/FAILURE
Jan 10 08:41:11 dev-elk-kb-7a-1.novalocal systemd[1]: Unit kibana.service entered failed state.
Jan 10 08:41:11 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service failed.
Jan 10 08:41:14 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service holdoff time over, scheduling restart.
Jan 10 08:41:14 dev-elk-kb-7a-1.novalocal systemd[1]: Stopped Kibana.
Jan 10 08:41:14 dev-elk-kb-7a-1.novalocal systemd[1]: start request repeated too quickly for kibana.service
Jan 10 08:41:14 dev-elk-kb-7a-1.novalocal systemd[1]: Failed to start Kibana.
Jan 10 08:41:14 dev-elk-kb-7a-1.novalocal systemd[1]: Unit kibana.service entered failed state.
Jan 10 08:41:14 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service failed.
[centos@dev-elk-kb-7a-1 ~]$ timed out waiting for input: auto-logout

```

---

<div class="post-metadata">

**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\
**Post date:** [January 10, 2022, 5:09pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/2 "2022-01-10T17:09:32Z")

</div>

Hi, @abhayamishra. The attached logs don't look like written by Kibana. Could you run Kibana with `--verbose` flag and the generated logs?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 11, 2022, 12:22am UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/3 "2022-01-11T00:22:05Z")

</div>

Welcome to our community! 😃

You will need to look in `/var/log/kibana/kibana.log`, as it will have more information.

---

<div class="post-metadata">

**Author:** ![abhayamishra](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@abhayamishra](https://discuss.elastic.co/u/abhayamishra)\
**Post date:** [January 11, 2022, 5:30am UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/4 "2022-01-11T05:30:57Z")

</div>

Ahh!!!.. Forgot to mention, there is NO logs getting generated, as soon as I do upgrade or install this version, so unable to identify issue.  
Attached --verbose flag, sharing output.

```auto
[centos@dev-elk-kb-7a-1 ~]$ systemctl status -l kibana
● kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2022-01-11 05:26:45 UTC; 18s ago
     Docs: https://www.elastic.co
  Process: 1097 ExecStart=/usr/share/kibana/bin/kibana --logging.dest="/var/log/kibana/kibana.log" --pid.file="/run/kibana/kibana.pid" --verbose (code=exited, status=1/FAILURE)
 Main PID: 1097 (code=exited, status=1/FAILURE)

Jan 11 05:26:42 dev-elk-kb-7a-1.novalocal systemd[1]: Unit kibana.service entered failed state.
Jan 11 05:26:42 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service failed.
Jan 11 05:26:45 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service holdoff time over, scheduling restart.
Jan 11 05:26:45 dev-elk-kb-7a-1.novalocal systemd[1]: Stopped Kibana.
Jan 11 05:26:45 dev-elk-kb-7a-1.novalocal systemd[1]: start request repeated too quickly for kibana.service
Jan 11 05:26:45 dev-elk-kb-7a-1.novalocal systemd[1]: Failed to start Kibana.
Jan 11 05:26:45 dev-elk-kb-7a-1.novalocal systemd[1]: Unit kibana.service entered failed state.
Jan 11 05:26:45 dev-elk-kb-7a-1.novalocal systemd[1]: kibana.service failed.

```

Last logs generated yesterday, before upgrade, after upgrade there is no logs getting generated.

```auto
{"type":"log","@timestamp":"2022-01-10T08:37:10Z","tags":["info","plugins-system"],"pid":14995,"message":"Stopping all plugins."}

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 11, 2022, 5:38am UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/5 "2022-01-11T05:38:39Z")

</div>

Please share more of the Kibana log.

---

<div class="post-metadata">

**Author:** ![abhayamishra](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@abhayamishra](https://discuss.elastic.co/u/abhayamishra)\
**Post date:** [January 11, 2022, 6:06am UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/6 "2022-01-11T06:06:33Z")

</div>

After upgrade or fresh install of 7.16.1, there is no logs getting generated.

Should we possibly look into some configuration?

---

<div class="post-metadata">

**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\
**Post date:** [January 11, 2022, 12:52pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/7 "2022-01-11T12:52:52Z")

</div>

> [@abhayamishra](#):
>
> Should we possibly look into some configuration?

Let's give it a try, could you attach your config file?

Are you sure your orchestration system runs Kibana?

---

<div class="post-metadata">

**Author:** ![abhayamishra](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@abhayamishra](https://discuss.elastic.co/u/abhayamishra)\
**Post date:** [January 11, 2022, 2:54pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/8 "2022-01-11T14:54:19Z")

</div>

Yes, This is all working before upgrading it from 7.5.2, to 7.16.1. After upgrade to 7.16.1, server is not getting started. There are still other servers where Kibana 7.5.2 is running and no issue. We are trying to upgrade due to Log4j Vulnerability (although this is not impacted, but ES and Logstash are already upgraded to 7.16.1)

Kibana.yml

```auto
server.port: 5601
server.host: "0.0.0.0"
server.basePath: ""
server.maxPayloadBytes: 1048576
server.name: "dev-elk-kb-7b-1-10.220.xxx.xx"
elasticsearch.hosts: "https://read-es.elk-xxx.xxx.regn.net:9200"
elasticsearch.preserveHost: true
kibana.index: ".kibana"
kibana.defaultAppId: "discover"
server.ssl.enabled: true
server.ssl.certificate: /etc/kibana/WC-elk-ins.cert.pem
server.ssl.key: /etc/kibana/WC-elk-ins.key.pem
server.ssl.certificateAuthorities: ["/etc/kibana/elk-ins-ca.crt"]
elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/elk-ins-ca.crt"]
elasticsearch.ssl.verificationMode: none
elasticsearch.requestTimeout: 150000
elasticsearch.shardTimeout: 0
elasticsearch.startupTimeout: 5000
pid.file: /var/run/kibana/kibana.pid
logging.dest: /var/log/kibana/kibana.log
logging.quiet: true
logging.verbose: false
ops.interval: 5000
elasticsearch.username: "xxxx"
elasticsearch.password: "xxxx"
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.reporting.enabled: true
xpack.reporting.encryptionKey: "190923562656492345678901678901234545285761"
readonlyrest_kbn.login_custom_logo: 'https://xxx.xxx.com/-/media/images/logos/logo_.png'

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 11, 2022, 10:06pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/9 "2022-01-11T22:06:56Z")

</div>

I'd start by removing/disabling the read only rest plugin and seeing if this still happens.

---

<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:** [February 8, 2022, 10:07pm UTC](https://discuss.elastic.co/t/failed-to-start-kibana-7-16-1/293900/10 "2022-02-08T22:07:23Z")

</div>

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