Kibana service failed to start

Elastic Stack Kibana
1

Hi all, I hope that message finds you well.

I have installed elk version 7.17 on CentOS Linux release 7.9.2009.
I've tried to install kibana as a service, and it's failing to start.
Based on what I'm reading on other threads, it seems it's because I've started the service as root.
I'd appreciate some help on how to fix this please.

[root@BNH-ELK-LOG yum.repos.d]# sudo systemctl status kibana.service 
● kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Fri 2022-02-04 12:09:36 EST; 6min ago
     Docs: https://www.elastic.co
 Main PID: 25452 (code=exited, status=1/FAILURE)

Feb 04 12:09:33 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: kibana.service: main process exited, code=exited, status=1/FAILURE
Feb 04 12:09:33 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: Unit kibana.service entered failed state.
Feb 04 12:09:33 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: kibana.service failed.
Feb 04 12:09:36 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: kibana.service holdoff time over, scheduling restart.
Feb 04 12:09:36 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: Stopped Kibana.
Feb 04 12:09:36 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: start request repeated too quickly for kibana.service
Feb 04 12:09:36 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: Failed to start Kibana.
Feb 04 12:09:36 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: Unit kibana.service entered failed state.
Feb 04 12:09:36 BNH-ELK-LOG.binuh.dpko.un.org systemd[1]: kibana.service failed.
2

@jbudz I hope you don't mind me tagging you on this. You provided some very useful help on the thread below: Kibana Service Failed to start - #13 by jbudz

I was hoping you could give me some feedback on how to fix my issue :slight_smile:

3

Hey,

Can you share any error logs in /var/log/kibana/kibana.log?

4

Thank yo u for the quick reply.
Let me know if you need anything else.

[netadmin@BNH-ELK-LOG ~]$ sudo cat /var/log/kibana/kibana.log
[sudo] password for netadmin: 
{"type":"log","@timestamp":"2022-02-04T12:17:01-05:00","tags":["info","plugins-service"],"pid":27647,"message":"Plugin \"metricsEntities\" is disabled."}
{"type":"log","@timestamp":"2022-02-04T12:18:21-05:00","tags":["info","plugins-service"],"pid":28069,"message":"Plugin \"metricsEntities\" is disabled."}
{"type":"log","@timestamp":"2022-02-04T12:41:26-05:00","tags":["info","plugins-service"],"pid":1334,"message":"Plugin \"metricsEntities\" is disabled."}
{"type":"log","@timestamp":"2022-02-21T12:18:24-05:00","tags":["info","plugins-service"],"pid":14830,"message":"Plugin \"metricsEntities\" is disabled."}
{"type":"log","@timestamp":"2022-02-22T11:46:27-05:00","tags":["info","plugins-service"],"pid":13557,"message":"Plugin \"metricsEntities\" is disabled."}
[netadmin@BNH-ELK-LOG ~]$
5

@jbudz what are your thoughts? :slight_smile:

6

ok, so here's what I've tried so far:
in kibana.yml:
server.port: 5601
server.host: "0.0.0.0"

I changed the Elasticsearch username and pwd to the following:

Elasticsearch.username: "elastic"
Elasticsearch.password: "changeme"

I activated the following firewall ports:

sudo firewall-cmd --permanent --zone=public --add-port=9200/tcp
sudo firewall-cmd --permanent --zone=public --add-port=5601/tcp
sudo firewall-cmd --reload

Not much has changed so far.

7

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