Kibana not coming up after X-PACK Installation

Hi Team,

I have installed X-PACK on Kibana and after installation the kibana is not coming up.

[root@elk log]# sudo systemctl status kibana
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2018-05-29 04:37:38 EDT; 2min 14s ago
Process: 3960 ExecStart=/usr/share/kibana/bin/kibana -c /etc/kibana/kibana.yml (code=exited, status=1/FAILURE)
Main PID: 3960 (code=exited, status=1/FAILURE)

May 29 04:37:38 systemd[1]: kibana.service: main process exited, code=exited, status=1/FAILURE
May 29 04:37:38 systemd[1]: Unit kibana.service entered failed state.
May 29 04:37:38 systemd[1]: kibana.service failed.
May 29 04:37:38 systemd[1]: kibana.service holdoff time over, scheduling restart.
May 29 04:37:38 systemd[1]: start request repeated too quickly for kibana.service
May 29 04:37:38 systemd[1]: Failed to start Kibana.
May 29 04:37:38 systemd[1]: Unit kibana.service entered failed state.
May 29 04:37:38 systemd[1]: kibana.service failed.

Can anyone please help me with this issue.

Thanks in advance.

Kind Regards,
Asif Bhat

After re-installing the X-PACK I am able to bring the kibana service up but the URL is still down.

I am using the URL http://elk-stack.co

This is the kibana.conf file created during nginx setup -

server {
listen 80;

server_name elk-stack.co;

auth_basic "Restricted Access";
auth_basic_user_file /etc/nginx/.kibana-user;

location / {
    proxy_pass http://clm-pun-t2uslj:5601;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

Kind Regards,
Asif Bhat

What does this mean exactly?

What are the error you see ?
What are the errors you see in relevant parts of your nginx logs?
Can you access http://clm-pun-t2uslj:5601 directly ?

Please find my response inline -

What does this mean exactly?
ASIF : neither http://servername nor http://clm-pun-t2uslj:5601/ is working
What are the error you see ?
ASIF: what errors I need to check. Nginx logs or Kibana logs ?
What are the errors you see in relevant parts of your nginx logs?
ASIF:
2018/05/29 04:35:52 [error] 1391#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.28.220.114, server: elk-stack.co, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.1.1:5601/favicon.ico", host: "clm-pun-t2uslj", referrer: "http://clm-pun-t2uslj/"
2018/05/29 04:36:03 [error] 1391#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.28.220.114, server: elk-stack.co, request: "GET / HTTP/1.1", upstream: "http://127.0.1.1:5601/", host: "clm-pun-t2uslj"

Can you access http://clm-pun-t2uslj:5601 directly ?
ASIF: That is not accessible

Taking a step back, I guess you were using nginx for basic authentication to Kibana when you didn't have X-Pack installed. Do you want to keep nginx in front of kibana for some reason now, or can you use X-Pack security for Kibana authentication ?
It looks like all clm-pun-t2uslj, elk-stack.co are on localhost so maybe taking away nginx from your architecture will simplify things for you.

Can you also verify that kibana is actually up and running? What is the output of
sudo systemctl status kibana and sudo netstat -nlp | grep 5601 ?

It will also probably be beneficial for you to follow the steps in our documentation on how to install and setup x-pack in elasticsearch and in kibana respectively.

Kibana is up and running.

I also un-installed nginx and tried to use below URL and I am seeing the same issue.

http://clm-pun-t2xuxk:5601/

Kind Regards,
Asif Bhat

What is the issue you are seeing? What is the explicit error message you get ?

Have you configured kibana after installing X-Pack as described in the documentation? Can you share your kibana.yml with us?
Can you see any errors in your kibana.log file (located in /var/log/kibana ) ?

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