Troubleshooting

If you cannot access the Kibana Dashboard or you get no data in the Dashboard, use the following troubleshooting tips:

1. Verify that the StackLight Collector is running properly. For details, see the StackLight Collector troubleshooting instructions.

2. Verify that the nodes can connect to the Elasticsearch cluster through the virtual IP address on port 9200 as described in the Verifying Elasticsearch section.

3. On any of the Elasticsearch_Kibana role nodes, check the status of the virtual IP address and HAProxy resources on the Pacemaker cluster:

   root@node-1:~# crm resource status vip__es_vip_mgmt
   resource vip__es_vip_mgmt is running on: node-1.test.domain.local
   
   root@node-1:~# crm resource status p_haproxy
   resource p_haproxy is running on: node-1.test.domain.local
   

4. If the virtual IP or HAProxy resources are down, restart them:

   root@node-1:~# crm resource start vip__es_vip_mgmt
   root@node-1:~# crm resource start p_haproxy
   

5. Verify that the Elasticsearch server is up and running on both CentOS and Ubuntu:

   [root@node-1 ~]# /etc/init.d/elasticsearch-es-01 status
   

   If Elasticsearch is down, restart it on both CentOS and Ubuntu:

   [root@node-1 ~]# /etc/init.d/elasticsearch-es-01 start
   

6. Verify that Apache is up and running on both CentOS and Ubuntu:

   [root@node-1 ~]# /etc/init.d/apache2 status
   

   If Apache is down, restart it on both CentOS and Ubuntu:

   [root@node-1 ~]# /etc/init.d/apache2 start
   

7. Look for errors in the Elasticsearch log files located at /var/log/elasticsearch/es-01/.

8. Look for errors in the Apache log files located at /var/log/apache2/.