Follow

Kibana is not loading or is throwing an error

Issue

When attempting to load Kibana is not loading, or the UI returns a Status: Red error page:

Cause

This is likely caused by either:

  • Elasticsearch is not running
  • Authentication request to access Kibana is not being proxied correctly through Reporting 

Resolution Steps

In order to properly resolve this issue, there are several places to check:

  • Check Elasticsearch status on REPORTING NODE
  • Check interset.conf
  • Check kibana.yml

Check Elasticsearch status on REPORTING NODE

  1. SSH to the REPORTING NODE as the Interset User
  2. Type in the following command to check on the status of Elasticsearch:
    • For EL6
      • sudo service elasticsearch status
    • For EL7
      • sudo systemctl status elasticsearch
  3. If the Active status is inactive, this indicates that elasticsearch is not running. Type in the following command to start elasticsearch:
    • For EL6
      • sudo service elasticsearch start
    • For EL7
      • sudo systemctl start elasticsearch
  4. If the Active status is active (running), type in the following command to check if requests are being proxied through Reporting.
    • curl -u kibana:kibana localhost:19200/_cluster/health?pretty
  5. If the curl command succeeds, this indicates the system is configured correctly and the following will be outputted:
    •  {
    •   "cluster_name" : "interset",
    •   "status" : "green",
    •   "timed_out" : false,
    •   "number_of_nodes" : 4,
    •   "number_of_data_nodes" : 3,
    •   "active_primary_shards" : 152,
    •   "active_shards" : 304,
    •   "relocating_shards" : 0,
    •   "initializing_shards" : 0,
    •   "unassigned_shards" : 0,
    •   "delayed_unassigned_shards" : 0,
    •   "number_of_pending_tasks" : 0,
    •   "number_of_in_flight_fetch" : 0,
    •   "task_max_waiting_in_queue_millis" : 0,
    •   "active_shards_percent_as_number" : 100.0
    • }
  6. If the curl command fails, this indicates Elasticsearch is not proxying the authentication request properly via the interset.conf.

Check interset.conf

If the existing session to the REPORTING NODE is still active, please go directly to step 2

  1. SSH to the REPORTING NODE as the Interset User
  2. Type in the following command to edit the interset.conf to verify/modify a parameters and/or value:
    • sudo vi /etc/nginx/conf.d/interset.conf
  3. In the interset.conf, look for a section that is similar to the following:
    • server {
    •   listen 19200;
    •  
    •  location ~ ^/(.*)$ {
    •     keepalive_requests 0;
    •     proxy_pass http://127.0.0.1:9090/api/es/$1?$args;
    •     error_page 401 =302 $scheme://$host/api/actions/logoff;
    •   }
    • }
  4. Ensure the information listed in step 3 is set within the interset.conf. If it is not, modify accordingly.
  5. Once the changes have been made to the interset.conf, save and exit the file.
  6. In order for the changes to take effect, please type in the following to restart nginx:
    • For EL6
      • sudo service nginx restart
    • For EL7
      • sudo systemctl restart nginx

Check Kibana.yml

If the existing session to the REPORTING NODE is still active, please go directly to step 2.

  1. SSH to the REPORTING NODE as the Interset User
  2. Type in the following command to edit the kibana.yml file:
    • sudo vi /etc/kibana/kibana.yml
  3. In the kibana.yml file, look for the following:
    • elasticsearch.url:
  4. Ensure the parameter and value is set to the following:
  5. Once the changes have been made to the kibana.yml, save and exit the file.
  6. In order for the changes to take effect, please type in the following to restart kibana:
    • For EL6
      • sudo service kibana restart
    • For EL7
      • sudo systemctl restart kibana
  7. After a restart of kibana, type in the following command to restart Reporting:
    • For EL6
      • sudo service reporting restart
    • For EL7
      • sudo systemctl restart reporting

Once all the steps are completed, please attempt to access Kibana again to validate the steps have resolved the issue.

If the issue still persists, please contact Interset Support (support@interset.com)

Applies To

  • Interset 5.4.x or higher 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments